| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| projects:frontier-team-builder [2023/12/03 05:48] – oemb1905 | projects:frontier-team-builder [2023/12/03 06:44] – oemb1905 |
|---|
| Require valid-user | Require valid-user |
| | |
| | This takes care of password protecting the development instance and ensuring that LTS is enforced for all url requests. After that, it's now time to set permissions for the production instance. To do that, let's ensure we have some common read/write/execute permissions on the instance. These are recommendations and took me about 1-2 hours of code review to decide a) what was needed for things to function and b) what we could restrict without harming functionality. Here's the script I came up with; make sure to adjust for the ''domain.com'' and other settings unique to your workflow: |
| | |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/projects/permissions.sh|permissions.sh]] |
| | |
| | Next, we need to harden the production instance and/or optionally white-label it. To harden, we remove the development cog from footer.php and make write.php an empty file. Here's the changes we made: |
| | |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/projects/custom/src/index.php|index.php]] |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/projects/custom/src/footer.php|footer.php]] |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/projects/custom/src/data/write.php|write.php]] |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/tree/main/projects/custom/src/img|img]] |
| | |
| | Now, the repository also has the ability to store overrides on moves and custom meta groups, however, this is optional and more of a choice specific to each meta development team. |
| | |
| | ------------------------------------------- |
| | |
| | At this point, the development and production virtual hosts are created, secured sufficiently, and/or optionally customized. From this point forward, the tutorial is no longer about how to set up the instances, but rather how to leverage those instances to create metas on the development instance and then migrate those development changes to production. In order to do this, one needs to have detailed understanding of how the upstream code from pvpoke.com works. For me, this took weeks of studying the code with a colleague of mine at Antimatter.GG gaming, meetings with the head developer of pvpoke.com, and a bit of trial and error. Once that was done, I created two scripts. The first one creates the pre-requisite back-end files needed for the creation of a new meta on the development instance, and the second one merges the metas you created in development back to production while preserving aforementioned white-labeling and hardening. Below, I've included the wiki post KakunaMatata made about how his stack works, the pre-requisite file creation script, and the merge to production script: |
| | |
| | *[[https://github.com/pvpoke/pvpoke/wiki/Creating-New-Cups-&-Rankings|Creating New Cups]] |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/projects/poke-create-files.sh|poke-create-files.sh]] |
| | *[[https://repo.haacksnetworking.org/haacknet/haackingclub/-/blob/main/projects/poke-rebuild-production.sh|poke-rebuild-production.sh]] |
| | |
| | |
| | |
| | |
| |
| |
| |
| --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/12/03 04:48// | --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/12/03 04:48// |
