No description
Find a file
2024-11-04 09:53:26 -06:00
migrate Use sales summary instead of sales 2024-10-21 12:06:16 -05:00
schema Add basic schema 2024-10-28 16:40:40 -05:00
src umami shift. 2024-11-04 09:53:26 -06:00
static A huge swing for the outfield. 2024-10-18 15:08:06 -05:00
.gitignore gitignore. 2024-10-28 16:41:48 -05:00
.npmrc Initial commit 2024-10-11 17:59:10 -05:00
.prettierignore Initial commit 2024-10-11 17:59:10 -05:00
.prettierrc A huge swing for the outfield. 2024-10-18 15:08:06 -05:00
eslint.config.js Initial commit 2024-10-11 17:59:10 -05:00
LICENSE.md Update LICENSE.md 2024-10-28 20:16:48 +00:00
nginx.conf spacing 2024-10-19 15:09:57 -05:00
package-lock.json Add page for closed. 2024-10-24 16:48:21 -05:00
package.json Add page for closed. 2024-10-24 16:48:21 -05:00
README.md readme. 2024-10-28 16:45:49 -05:00
svelte.config.js A huge swing for the outfield. 2024-10-18 15:08:06 -05:00
vite.config.js Initial commit 2024-10-11 17:59:10 -05:00

MHS Membership Remix

This is a rewrite of the original MHS Membership database application that was written using node and mongo. It was decided to rewrite for ease of revision going forward. This application is a Single Page Application (SPA) using Svelte (with Sveltekit) for the client application and pocketbase to store all of the data, which means everything ends up in an easily backed up SQLite database on the server.

Developing on this codebase.

You will need a local version of pocketbase with the latest schema (which may be imported from the schema/pb_schema.json file).

Once you have those, clone this repo, then run these commands to start a dev server:

npm install
npm run dev -- --open # You can omit the '-- --open' if you don't want to open a browser window.

Building

To build for production, you can run the following command:

npm run build

You can preview the production build with npm run preview.

Deploying

This SPA app is automatically deployed when a new change is pushed to the main branch.

If there are any updates to the schema, please export from your pocketbase and change the schema/pb_schema.json file to match. Then push the lastest code changes, and while that is updated, import the change to the deployed pocketbase. You will need to be an admin on the production pocketbase to perform that task.