Hello everyone. I ran into a problem while developing discourse I usually clone files from Git Making changes Making a commit on Git My teammate does a git pull And gets all my changes How can I implement something similar in discourse? How can I make changes so that other people can install them at home?

Thanks for the reply. Yes, you are right about the topic. What about the synchronization of components and settings?

Your plugin code can define migrations and/or seed contents as necessary. They can also ensure that site settings have the appropriate value.

I want to clone my installation completely

You can take a backup and restore where needed.

I tried it. I get an error when restoring [image] The copy does not appear in the list after even 30 minutes

I like to use S3 for backups and then all sites can share the same backup set. Then when you do a backup on production, you can immediately restore it on your staging sites to see that it works with the current data.

Amazon S3 - Cloud Object Storage - AWS Amazon S3 is cloud object storage with industry-leading scalability, data availability, security, and performance. S3 is ideal for data lakes, mobile applications, backup and restore, archival, IoT devices, ML, AI, and analytics.

Using Object Storage for Uploads (S3 & Clones) Setting up file and image uploads to S3 are where to start. For backups only its quite simple. Backblaze and wasabi are cheap. Also storj.io has a product that I’ve used for backups.

Just my 10 cents, and not to take away from the helpful comments here on backups, but stepping back a bit: I’m really not sure if ‘synchronising’ installs of Discourse is worth much effort. Unless you intend on PRing into Discourse core, developing plugins or TCs is where it’s at and gives you the most robust, efficient solution for customisation. The key thing with developing Plugins and Theme Components is they will be deployed to multiple instances of Discourse over which you may not have control in any case? So having a slightly unique local Discourse instance for development is totally ok. (within reason) The key workflow should involve keeping the plugin or TC up to date in a shared repo, most likely on Github.

איך לפתח דיון בצוות?

מפתח

Mikhail_Tyuftyaev (Mikhail Tyuftyaev) 1 ביולי,‏ 2021,‏ 7:14am 9

What it is S3? I would like to use this

נושא		תגובות	צפיות
Digital Ocean + GitHub Development	4	443	24 במרץ,‏ 2024
What is the recommended workflow for managing a live Discourse site? Product Support	4	1479	15 במאי,‏ 2018
Extend built-in backup remote destination options Feature backups	4	932	25 בינואר,‏ 2023
Problems with understanding the development of Discourse Development	5	1485	14 ביולי,‏ 2021
Understanding the development/deployment process Development	4	1534	18 ביולי,‏ 2018

איך לפתח דיון בצוות?

נושאים קשורים