1
0
Fork 0
photos/web/manage
Ambrose Chua aeddf1c9d6 Add uploader 2021-11-17 11:06:37 +08:00
..
src Add uploader 2021-11-17 11:06:37 +08:00
.gitignore WIP: Initial web gallery 2020-06-13 14:49:35 +08:00
Dockerfile Initial manage scaffold in Svelte 2020-06-09 00:53:41 +08:00
Makefile Switch gallery layout engine into a single function 2020-10-11 22:22:29 +08:00
README.md Initial manage scaffold in Svelte 2020-06-09 00:53:41 +08:00
index.tmpl Switch gallery layout engine into a single function 2020-10-11 22:22:29 +08:00
indextmpl.go Switch gallery layout engine into a single function 2020-10-11 22:22:29 +08:00
package.json WIP: Initial web gallery 2020-06-13 14:49:35 +08:00
rollup.config.js WIP: Initial web gallery 2020-06-13 14:49:35 +08:00

README.md

svelte app

Get started

Install the dependencies...

npm install

...then start Rollup:

npm run dev

Navigate to localhost:5000. You should see your app running. Edit a component file in src, save it, and reload the page to see your changes.

By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv commands in package.json to include the option --host 0.0.0.0.

Building and running in production mode

To create an optimised version of the app:

npm run build

You can run the newly built app with npm run start. This uses sirv, which is included in your package.json's dependencies so that the app will work when you deploy to platforms like Heroku.

Single-page app mode

By default, sirv will only respond to requests that match files in public. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.

If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start" command in package.json:

"start": "sirv public --single"