Skip to content

Releases: julianpoy/RecipeSage-selfhost

Selfhost Config v4.1.0 (For RecipeSage v2.14.x)

05 Jun 06:24
Compare
Choose a tag to compare

Updates RecipeSage to v2.14.x

See this section of the README, which is new related to features added in RecipeSage v2.14.x

All previous upgrade notes apply if you're coming from an earlier version.

Selfhost Config v4.0.0 (For RecipeSage v2.13.3)

17 Jan 00:06
1e3e12e
Compare
Choose a tag to compare

Upgrading - IMPORTANT

Migrations are now automated, and use a different migration tool.

If you have an older version of this repository, you must upgrade to this version of the repository and do the following before upgrading to newer versions so that migrations all line up:

  1. Update your local copy of the repository to v4.0.0. If you've made any changes to your docker-compose.yaml file, please note that much has changed in the official docker-compose.yaml file and you must update accordingly.
  2. Run docker compose exec api tsx packages/backend/src/migrate
  3. If the command prior ran successfully, run docker compose exec api npx prisma migrate resolve --applied 0_init
  4. Restart the API container with docker compose restart api

If you do not perform the steps above, you will see database errors related to missing columns and the app will not function.

What's Changed

  • Improve podman support by @MathieuMoalic in #60
  • Improved Synology support with dedicated instructions (please file an issue if they're incorrect)
  • Breaking changes related to migration management, as the official RecipeSage repo has moved to a new ORM. See upgrade notes if you're upgrading from an older version.

New Contributors

Full Changelog: v3.1.0...v4.0.0

Selfhost Config v3.1.0 (For RecipeSage v2.11.5)

17 Sep 20:37
899be2d
Compare
Choose a tag to compare

What's Changed

  • Update for compose V2 by @Evs91 in #56
  • Now uses more fixed-version tags for clarity and ease of upgradability
  • ARM support in full. All containers now support running on ARM platforms.

New Contributors

  • @Evs91 made their first contribution in #56

Full Changelog: v3.0.0...v3.1.0

v3.0.0

18 Aug 23:44
484bf0f
Compare
Choose a tag to compare

Full Changelog: v2.0.2...v3.0.0

v2.0.2

17 Jun 16:58
7e25aad
Compare
Choose a tag to compare

Full Changelog: v2.0.1...v2.0.2

v2.0.1

17 Apr 01:14
Compare
Choose a tag to compare

Bump recipesage to v2.11.0-beta10.

See this issue for some details if you'd like to remove Minio completely:

julianpoy/RecipeSage#796 (comment)

v2.0.0

09 Apr 16:39
9a0837b
Compare
Choose a tag to compare

Revamp selfhosting configs. Use local filesystem rather than minio.

Important upgrade notes: (none of this applies to new users, only those with existing data)

The new docker-compose.yml no longer uses minio, and instead writes directly to the local filesystem. You'll need to keep your minio instance from the old Dockerfile along with it's volume definition.

v1.2.1

15 Mar 03:45
4ea53f9
Compare
Choose a tag to compare

Fix issues with ElasticSearch.

v1.2.0

05 Nov 06:03
6d5eb1e
Compare
Choose a tag to compare

Update RecipeSage image to v2.9.0, ElasticSearch image to v8.4.3, and Browserless to 1.53.0.

Upgrade note: You must first upgrade your elasticsearch container image to v7.17 before upgrading to this new version.

v1.1.0

07 Mar 23:15
Compare
Choose a tag to compare

Move minio behind app proxy.

Note: If you're upgrading from an earlier version of these selfhost configs, you'll need to make sure to continue to expose 9000 on the Minio container in order to maintain access to images uploaded before this change, or update the image path in the DB.