VbzCart/install - Revision history

Woozle at 16:39, 14 October 2022

2022-10-14T16:39:39Z

@@ Line 1: / Line 1: @@
-'''Prerequisites''': Linux, [[PHP]] 7, [[MySQL]]-workalike, [[Apache web server|Apache]].
+===Preparation===
 This page will eventually need to include a lot more information, but for now the basic setup procedure is:
-* Clone the VbzCart Git repository at <code>git@gitlab.com:woozalia/VbzCart.git</code> into a folder of your choice, which we'll call {{arg|vbz-base}}.
+* Clone the VbzCart Git repository at <code>{{i/var/page|git.origin}}</code> into a folder of your choice, which we'll call {{arg|vbz-base}}.
 * Copy the <code>{{arg|vbz-base}}/config</code> folder to a location outside of <code>{{arg|vbz-base}}</code>.
 ** We'll call this new location {{arg|local-config}}.
@@ Line 9: / Line 11: @@
 * Modify each file to match your local environment, according to instructions in each file.
 * Optional: modify files in <code>{{arg|local-config}}/portable</code> as needed.
-* [[Ferreteria/install|Install Ferreteria]]
+* {{l/ferreteria/|install|Install Ferreteria}}
 * Set up database and tables (instructions to be written)
 * Link or copy the <code>{{arg|local-config}}/portable/index.php</code> file to your public web folder.
 * Link or copy the <code>{{arg|vbz-base}}/static</code> folder to your public web folder.
 * Create the public web ufiles folder
-'''4.''' If you haven't already, make a <code>dropins</code> folder under <code>site</code>. Link or copy all the dropins you want to use from VbzCart into that folder.
+For the canonical setup at vbz.net, see {{l/wooz|VbzCart/setup|wooz.dev}}.

Woozle: /* Steps */

2022-10-14T14:01:07Z

Steps

← Older revision		Revision as of 14:01, 14 October 2022
Line 19:		Line 19:
	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.		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===		===Steps===
	'''1.''' ~~[[Ferreteria~~/install\|Install Ferreteria]] (you can actually do this at any point, but it may be easier to do it first).		<poem>
			'''1.''' {{l/ferreteria/\|install\|Install Ferreteria}} (you can actually do this at any point, but it may be easier to do it first).
	'''2.''' Run these commands in a terminal on your web server (you can skip <code>[[mkdir]]</code> wherever the folder already exists):		'''2.''' Run these commands in a terminal on your web server (you can skip <code>[[mkdir]]</code> wherever the folder already exists):</poem>
	* cd {{arg\|$HOME}}		* cd {{arg\|$HOME}}
	* su {{arg\|$USER}}		* su {{arg\|$USER}}

Woozle at 13:48, 14 October 2022

2022-10-14T13:48:45Z

← Older revision		Revision as of 13:48, 14 October 2022
Line 2:		Line 2:

	This page will eventually need to include a lot more information, but for now the basic setup procedure is:		This page will eventually need to include a lot more information, but for now the basic setup procedure is:
	* Clone the VbzCart Git repository at <code>[git@gitlab.com:woozalia/VbzCart.git</code> into a folder of your choice, which we'll call {{arg\|vbz-base}}.		* Clone the VbzCart Git repository at <code>git@gitlab.com:woozalia/VbzCart.git</code> into a folder of your choice, which we'll call {{arg\|vbz-base}}.
	* Copy the <code>{{arg\|vbz-base}}/config</code> folder to a location outside of <code>{{arg\|vbz-base}}</code>.		* Copy the <code>{{arg\|vbz-base}}/config</code> folder to a location outside of <code>{{arg\|vbz-base}}</code>.
	** We'll call this new location {{arg\|local-config}}.		** We'll call this new location {{arg\|local-config}}.

Woozle: /* Steps */ dropins

2019-10-27T21:56:57Z

Steps: dropins

← Older revision		Revision as of 21:56, 27 October 2019
Line 45:		Line 45:

	At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.		At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.

			'''4.''' If you haven't already, make a <code>dropins</code> folder under <code>site</code>. Link or copy all the dropins you want to use from VbzCart into that folder.

Woozle: /* Steps */ TODO is now done

2019-10-13T19:27:14Z

Steps: TODO is now done

← Older revision		Revision as of 19:27, 13 October 2019
Line 45:		Line 45:

	At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.		At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.

	~~TODO: configure .htaccess to properly intercept virtual URLs~~

Woozle: /* Steps */ correction

2019-10-13T19:26:46Z

Steps: correction

← Older revision		Revision as of 19:26, 13 October 2019
Line 34:		Line 34:
	* mv vbzcart/examples vbzcart/local		* mv vbzcart/examples vbzcart/local
	* ln -rs vbzcart/local/index.php ~/public_html/		* ln -rs vbzcart/local/index.php ~/public_html/
	* ln -rs vbzcart/~~local~~/.htaccess ~/public_html/		* ln -rs vbzcart/portable/.htaccess ~/public_html/
	* cd ..		* cd ..
	* ln -rs git/VbzCart/static ~/public_html/static		* ln -rs git/VbzCart/static ~/public_html/static

Woozle: /* Steps */ .htaccess

2019-10-13T19:25:06Z

Steps: .htaccess

← Older revision		Revision as of 19:25, 13 October 2019
Line 33:		Line 33:
	* cp -R ../git/VbzCart/config vbzcart		* cp -R ../git/VbzCart/config vbzcart
	* mv vbzcart/examples vbzcart/local		* mv vbzcart/examples vbzcart/local
	* ln -rs vbzcart/local/index.php ~/public_html/~~index~~.~~php~~		* ln -rs vbzcart/local/index.php ~/public_html/
			* ln -rs vbzcart/local/.htaccess ~/public_html/
	* cd ..		* cd ..
	* ln -rs git/VbzCart/static ~/public_html/static		* ln -rs git/VbzCart/static ~/public_html/static

Woozle at 13:45, 12 October 2019

2019-10-12T13:45:50Z

← Older revision		Revision as of 13:45, 12 October 2019
Line 13:		Line 13:
	* Link or copy the <code>{{arg\|local-config}}/portable/index.php</code> file to your public web folder.		* Link or copy the <code>{{arg\|local-config}}/portable/index.php</code> file to your public web folder.
	* Link or copy the <code>{{arg\|vbz-base}}/static</code> folder to your public web folder.		* Link or copy the <code>{{arg\|vbz-base}}/static</code> folder to your public web folder.
			* Create the public web ufiles folder
	==Woozle's setup==		==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):		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):
Line 35:		Line 36:
	* cd ..		* cd ..
	* ln -rs git/VbzCart/static ~/public_html/static		* ln -rs git/VbzCart/static ~/public_html/static
			* mkdir ufiles
			* cd ufiles
			* mkdir pub
			* ln -rs pub ~/public_html/ufiles

	'''3.''' Modify the files in <code>vbzcart/local</code> as needed to match your local environment. (If you use the same structure I'm using here, <code>index.php</code> will not need modification.) This will require having a database set up so you can get the appropriate connection credentials to put in <code>creds.php</code>.		'''3.''' Modify the files in <code>vbzcart/local</code> as needed to match your local environment. (If you use the same structure I'm using here, <code>index.php</code> will not need modification.) This will require having a database set up so you can get the appropriate connection credentials to put in <code>creds.php</code>.

	At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.		At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.

			TODO: configure .htaccess to properly intercept virtual URLs

Woozle: another link to create

2019-10-12T12:29:01Z

another link to create

← Older revision		Revision as of 12:29, 12 October 2019
Line 11:		Line 11:
	* [[Ferreteria/install\|Install Ferreteria]]		* [[Ferreteria/install\|Install Ferreteria]]
	* Set up database and tables (instructions to be written)		* Set up database and tables (instructions to be written)
			* Link or copy the <code>{{arg\|local-config}}/portable/index.php</code> file to your public web folder.
			* Link or copy the <code>{{arg\|vbz-base}}/static</code> folder to your public web folder.
	==Woozle's setup==		==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):		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):
Line 31:		Line 33:
	* mv vbzcart/examples vbzcart/local		* mv vbzcart/examples vbzcart/local
	* ln -rs vbzcart/local/index.php ~/public_html/index.php		* ln -rs vbzcart/local/index.php ~/public_html/index.php
			* cd ..
			* ln -rs git/VbzCart/static ~/public_html/static

	'''3.''' Modify the files in <code>vbzcart/local</code> as needed to match your local environment. (If you use the same structure I'm using here, <code>index.php</code> will not need modification.) This will require having a database set up so you can get the appropriate connection credentials to put in <code>creds.php</code>.		'''3.''' Modify the files in <code>vbzcart/local</code> as needed to match your local environment. (If you use the same structure I'm using here, <code>index.php</code> will not need modification.) This will require having a database set up so you can get the appropriate connection credentials to put in <code>creds.php</code>.

	At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.		At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.

Woozle: /* Steps */

2019-10-10T22:52:22Z

Steps

← Older revision		Revision as of 22:52, 10 October 2019
Line 32:		Line 32:
	* ln -rs vbzcart/local/index.php ~/public_html/index.php		* ln -rs vbzcart/local/index.php ~/public_html/index.php

	Modify the files in <code>vbzcart/local</code> as needed to match your local environment. (If you use the same structure I'm using here, <code>index.php</code> will not need modification.) This will require having a database set up so you can get the appropriate connection credentials to put in <code>creds.php</code>.		'''3.''' Modify the files in <code>vbzcart/local</code> as needed to match your local environment. (If you use the same structure I'm using here, <code>index.php</code> will not need modification.) This will require having a database set up so you can get the appropriate connection credentials to put in <code>creds.php</code>.

	At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.		At this point, I ''think'' you should be able to point a browser at the domain and get something, even if it's only errors that you'll need to look at in order to figure out what's left to configure.