cd app
DROPBOX_FOLDER_PATH=/www/ DROPBOX_SECRET=xxx DROPBOX_ACCESS_TOKEN=xxx npm run start
DROPBOX_FOLDER_PATH=/www/ DROPBOX_SECRET=xxx DROPBOX_ACCESS_TOKEN=xxx docker build . -t now-react-static:initial
docker run -e DROPBOX_ACCESS_TOKEN -e DROPBOX_SECRET -e DROPBOX_FOLDER_PATH -p8004:8004 now-react-static:initial
First install now Desktop and you get the now command line tool.
In Dropbox, login and go to /development and from that URL you can add a new v2 app with a unique name of your choice, and full access. You can then generate an access token.
Once that's done, install the Dropbox desktop client and add a directory named www to share with people who should be able to change the website. Inside the www directory create a file index.md with this content:
This is a *very* nice sentence.
Unfortunately you can't add .js files directly in the web interface.
Deploy a new instance like this, specifying the Dropbox access token, secret and the remote folder path instead of xxx like this:
now --public -e DROPBOX_SECRET=xxx -e DROPBOX_REMOTE_FOLDER_PATH=/www/ -e DROPBOX_ACCESS_TOKEN=xxx
now alias set glabs-canvas-marketing-ybyqnndesl.now.sh canvas.glabs.jimmyg.org
Now visit the URL created by the deployment.
There is some more information about now deployments and aliases in the next section.
You can see your apps like this:
now ls
> 8 total deployments found under <hidden email> [293ms]
> To list more deployments for an app run `now ls [app]`
app url inst # type state age
now-react-static now-react-static-grnfyhsggu.now.sh - DOCKER READY 21h
app app-fdfhkrkfrf.now.sh 0 NPM READY 1d
now-gatsby now-gatsby-xqyojmxgrt.now.sh - DOCKER ERROR 1d
niw niw-bizozygewq.now.sh - DOCKER READY 43d
You can see each instance for each app like this:
now ls now-react-static
> 5 total deployments found under <hidden email> [311ms]
> To list deployment instances run `now ls --all [app]`
app url inst # type state age
now-react-static now-react-static-grnfyhsggu.now.sh - DOCKER READY 21h
now-react-static now-react-static-knbhjzxoqy.now.sh - DOCKER READY 1d
now-react-static now-react-static-tdvckogbkr.now.sh - DOCKER READY 1d
now-react-static now-react-static-bvvjprsdow.now.sh - DOCKER READY 1d
now-react-static now-react-static-dpbxrixxlp.now.sh - DOCKER READY 1d
Now, it would be annoying to have to tell everyone a new URL each time you made a change, so instead you can create a now alias for a particular instance and give that out to people instead. You can do so like this:
$ now alias set now-react-static-grnfyhsggu.now.sh glabs-canvas.now.sh
> Assigning alias glabs-canvas.now.sh to deployment now-react-static-grnfyhsggu.now.sh
> Success! glabs-canvas.now.sh now points to now-react-static-grnfyhsggu.now.sh [3s]
This now means that you can give out glabs-canvas.now.sh as a URL and it will currently point to the same instance as the now-react-static-grnfyhsggu.now.sh URL.
It isn't always appropriate to use a domain ending in .now.sh. You might want to use your own custom domain instead. Zeit now allows you to do this is you can first prove you own the domain. Here's an example of setting up the same instance to be accessible at the domain canvas.glabs.jimmyg.org but you could equally well use myapp.com or somedomain.org if you owned them:
now alias set now-react-static-grnfyhsggu.now.sh canvas.glabs.jimmyg.org
The first time you try this you'll get an error message asking you to prove you
own the domain by adding a TXT record to your domain. TXT records are just
a type of DNS record (you would only be able to do this if you owned the
domain).
Here's the first attempt that fails:
now alias set now-react-static-grnfyhsggu.now.sh canvas.glabs.jimmyg.org
> Assigning alias canvas.glabs.jimmyg.org to deployment now-react-static-grnfyhsggu.now.sh
> Nameservers: ns-1858.awsdns-40.co.uk, ns-972.awsdns-57.net, ns-166.awsdns-20.com, ns-1273.awsdns-31.org
> Error! We couldn't verify the domain jimmyg.org.
Please make sure that your nameservers point to zeit.world.
Examples: (full list at https://zeit.world)
a.zeit.world 96.45.80.1
b.zeit.world 46.31.236.1
c.zeit.world 43.247.170.1
As an alternative, you can add following records to your DNS settings:
name type value
_now TXT a1a6add8943a890f6f239ad05f6a9a7d25a3e863db6803f9a57f4b05c314a396
ALIAS alias.zeit.co
If you now add the value as a TXT record under the _now subdomain and then alias your custom domain to alias.zeit.co and try again, Zeit now will check the record and this time the alias will succeed.
Here is what my DNS looks like:
_now.jimmyg.org. 300 TXT a1a6add8943a890f6f239ad05f6a9a7d25a3e863db6803f9a57f4b05c314a396
canvas.glabs.jimmyg.org. 300 CNAME alias.zeit.co.
You need to add the TXT record to prove you own the domain, and the CNAME or ALIAS record so that the DNS points to the right place.
Running the command again gives:
now alias set now-react-static-grnfyhsggu.now.sh canvas.glabs.jimmyg.org
> Assigning alias canvas.glabs.jimmyg.org to deployment now-react-static-grnfyhsggu.now.sh
> Nameservers: ns-166.awsdns-20.com, ns-972.awsdns-57.net, ns-1273.awsdns-31.org, ns-1858.awsdns-40.co.uk
> Success! Domain jimmyg.org added!
> Certificate for canvas.glabs.jimmyg.org (cert_QwJdkzPn4kPeEbZ) created [10s]
> Success! canvas.glabs.jimmyg.org now points to now-react-static-grnfyhsggu.now.sh [15s]
You can now visit your app by visiting https://canvas.glabs.jimmyg.org.
To see any errors in the console, start the server with this environment variable set:
DEBUG=true