Ferreteria/install: Difference between revisions

From Woozle Writes Code
Jump to navigation Jump to search
(Created page with "* Clone the [https://gitlab.com/woozalia/ferreteria/tree/v2 Ferreteria Git repository] <ref name=branch /> into a folder of your choice, which we'll call <code>[ferreteria bas...")
 
No edit summary
Line 1: Line 1:
* Clone the [https://gitlab.com/woozalia/ferreteria/tree/v2 Ferreteria Git repository] <ref name=branch /> into a folder of your choice, which we'll call <code>[ferreteria base]</code>.
* Clone the [https://gitlab.com/woozalia/ferreteria Ferreteria Git repository] into a folder of your choice, which we'll call {[arg|ferreteria base}}.
* Copy the <code>[ferreteria base]/config</code> folder to a location outside of <code>[ferreteria base]</code>.
* Copy the <code>{{arg|ferreteria base}}/config</code> folder to a location outside of <code>[ferreteria base]</code>.
** We'll call this new location <code>[local config]</code>.
** We'll call this new location <code>{{arg|local config}}</code>.
** My standard location for this is <code>/home/<user>/site/config/ferreteria</code>
** My [[User:Woozle/setups/vdomain|standard location]] for this is <code>/home/{{arg|user}}/site/config/ferreteria</code>
* Optional: Modify each file to match your local environment, according to instructions in each file.
* Optional: Modify each file to match your local environment, according to instructions in each file.
** There's currently only one file, <code>const.php</code>, and it normally won't need modifying.
** There's currently only one file, <code>const.php</code>, and it normally won't need modifying.
==Footnotes==
==Woozle's setup==
<references>
Some specifics of how I usually set things up these days, giving examples from the dev instance I'm setting up as I type this (see [[User:Woozle/setups/vdomain]] for definitions):
<ref name=branch>We're currently using the <code>v2</code> branch; this should probably become the <code>master</code> branch, once I figure out how. The v3 branch probably needs to be started over again.</ref>
===Preparation===
</references>
You'll need to have {{arg|$USER}}'s account set up with an [[ssh]] key that can access GitLab. At least, I ''think'' that's the requirement. It might be more GitLab-project-specific.
===Steps===
Run these commands in a terminal on your web server (you can skip <code>[[mkdir]]</code> wherever the folder already exists):
* cd {{arg|$HOME}}
* su {{arg|$USER}}
* [[mkdir]] site
* cd site
* mkdir git
* [[git clone]] git@gitlab.com:woozalia/ferreteria.git
* cd ..
* mkdir config
* cd config
* cp -R ../git/ferreteria/config ferreteria

Revision as of 22:50, 10 October 2019

  • Clone the Ferreteria Git repository into a folder of your choice, which we'll call {[arg|ferreteria base}}.
  • Copy the <ferreteria base>/config folder to a location outside of [ferreteria base].
    • We'll call this new location <local config>.
    • My standard location for this is /home/<user>/site/config/ferreteria
  • Optional: Modify each file to match your local environment, according to instructions in each file.
    • There's currently only one file, const.php, and it normally won't need modifying.

Woozle's setup

Some specifics of how I usually set things up these days, giving examples from the dev instance I'm setting up as I type this (see User:Woozle/setups/vdomain for definitions):

Preparation

You'll need to have <$USER>'s account set up with an ssh key that can access GitLab. At least, I think that's the requirement. It might be more GitLab-project-specific.

Steps

Run these commands in a terminal on your web server (you can skip mkdir wherever the folder already exists):

  • cd <$HOME>
  • su <$USER>
  • mkdir site
  • cd site
  • mkdir git
  • git clone git@gitlab.com:woozalia/ferreteria.git
  • cd ..
  • mkdir config
  • cd config
  • cp -R ../git/ferreteria/config ferreteria