Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add solution to save new version on native save click #15

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add solution to save new version on native save click #15

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,3 +42,8 @@ npm run build
## Deployment

The way the environment is setup at the time of writing (2022-12-02), there is only one deployed environment being present (which currently is a development environment, since this service hasn't been released yet). In order to deploy a new version of the app, you can follow the steps specified in `docs/ec2.md`

## Upgrading Strapi

We use a plugin called [Content Versioning](https://github.com/notum-cz/strapi-plugin-content-versioning) to handle versioning. We're also using its tweak which automatically saves new versions when you click on Strapi's native "Save" button. This requires [patch-package](https://www.npmjs.com/package/patch-package), and a [custom patch](https://github.com/notum-cz/strapi-plugin-content-versioning/tree/main/patches) to the Strapi version, written by the content versioning authors.
So, when you want to upgrade a Strapi version; first make sure it works smooth with the plugin. Then also make sure to see if they've pushed a patch to that new Strapi version, which you will have to copy and paste into `/patches` in this project.
2 changes: 1 addition & 1 deletion docs/database.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ The way the production environment is setup at the moment, the only machine that
!NOTE! Triple-check that you are on your local environment when doing this, and not ssh:d into RDS.

1. Enter `whoami`. This is only to make sure you are on your local machine. The output should be your user on your local machine (the username on the EC2 instance is more generic)
2. Enter your local postgres database by running `psql <database-name`
2. Enter your local postgres database by running `psql <database-name>`
3. NOTE: the following will remove everything in your database. Make sure you won't miss anything in it. If you're sure; run `DROP SCHEMA public CASCADE;` followed by `CREATE SCHEMA public;`
4. Run `psql <database-name> < <path-to-your-database-dump>`. This will populate the database according to your dump

Expand Down
Loading