DevelopmentVMHowto - Revision history

Q.kontinuum: Add more detailed instructions on applying the upgrades file, add info about slash having admin rights

2016-02-18T22:16:51Z

Add more detailed instructions on applying the upgrades file, add info about slash having admin rights

← Older revision		Revision as of 22:16, 18 February 2016
Line 4:		Line 4:
	The Slashdev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev VM and has many enhancements over the original version. It is a VM that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.		The Slashdev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev VM and has many enhancements over the original version. It is a VM that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

	Once you get the VM downloaded and the VirtualBox up and ~~ruining~~, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.		Once you get the VM downloaded and the VirtualBox up and running, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

	The VM has port forwarding setup to you local system for ssh and http.		The VM has port forwarding setup to you local system for ssh and http.
Line 14:		Line 14:

	<pre>ssh slash@127.0.0.1 -p 8022</pre>		<pre>ssh slash@127.0.0.1 -p 8022</pre>

			User slash is in groups sudo and adm, so '''if''' you want to get a root shell you can get it by entering

			<pre>sudo bash</pre>

			Caution: Normally you won't need a root shell here.

	For websites, Apache will use the name localhost instead of 127.0.0.1 so you will need to use:		For websites, Apache will use the name localhost instead of 127.0.0.1 so you will need to use:

	<pre>http://localhost:1337</pre>		<pre>http://localhost:1337</pre>

			Check if you can access external servers (will be required if you want to install additional packages or directly checkout from github). E.g.
			<pre>ping soylentnews.org</pre>
			If the domain name cannot be resolved, you might want to shutdown the VM and add a bridged network adapter in network settings.

	==Setup the Environment ==		==Setup the Environment ==
Line 37:		Line 47:
	<pre>mysql -u root slashdev</pre>		<pre>mysql -u root slashdev</pre>

			On the mysql prompt, to apply the upgrades file, enter
			<pre>mysql> source slashcode/sql/mysql/upgrades</pre>
	== Update Slash ==		== Update Slash ==
	Now lets update slash to our new code by running:		Now lets update slash to our new code by running:

Paulej72 at 02:03, 9 October 2014

2014-10-09T02:03:47Z

← Older revision		Revision as of 02:03, 9 October 2014
Line 29:		Line 29:
	</pre>		</pre>

	There are a couple of scripts set up in the vm that make deploying and reloading ~~slashcode~~ easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the ~~slashcode~~ to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.		There are a couple of scripts set up in the vm that make deploying and reloading Slashcode easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the Slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.

	== MySQL Updates ==		== MySQL Updates ==
	We need to update the ~~dev~~ environment to work with the new ~~slashcode~~. The update files are normally in /srv/slashdev/slashcode/sql/mysql/. The upgrades file has the latest updates since that last major version of slashcode. The 14.10 version of the vm is fully up-to-date with with the 14.10 release of ~~the slashcode~~, so no updates to MySQL are needed. You will need to add any future DB updates that are listed in the upgrades file to keep the new code working properly.		We sometimes need to update the Slashdev environment to work with the new Slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/upgrades. The upgrades file has the latest updates since that last major version of slashcode. The 14.10 version of the VM is fully up-to-date with with the 14.10 release of Slashcode, so no updates to MySQL are currently needed. You will need to add any future DB updates that are listed in the upgrades file to keep the new code working properly.

	MySQL is accessed with root as the user and the database slashdev. To access the DB use the command:		MySQL is accessed with root as the user and the database slashdev. To access the DB use the command:
Line 44:		Line 44:
	To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.		To do simple updates, you would make changes to the files in slashcode and redeploy using the deployslash.sh script.

	What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the ~~slashcode~~ site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.		What if you want to develop code and have it merged into the main repo? In this case you will need to setup your own copy of the repo do do your development work. First if you do not have your own account on GitHub please set one up. Next go to the Slashcode site https://github.com/SoylentNews/slashcode and click on Fork in the upper right. Fork the repo to your user account.

	Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:		Now on the VM go to slashcode. We will setup your copy of the repo as a remote. Run the commands:
Line 56:		Line 56:

	Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers. See [[GitUse]] for more info about using git.		Once you get code you like, and have it committed to your personal fork, you can do a Pull Request, https://help.github.com/articles/using-pull-requests, that will create a ticket for the SoylentNews/slashcode repo to merge your commits to the master branch. After proper testing by the Dev team and other sanity checks, you code will be merged and eventually put on to the production servers. See [[GitUse]] for more info about using git.


	Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.		Just a note: I am new to git, so the above directions are what I have been using. If people have a better method for doing this please feel free to update this page with the new information --pauulej72.

	[[Category:Development]]		[[Category:Development]]

Paulej72: /* Download and Install VM */

2014-10-09T01:54:12Z

Download and Install VM

← Older revision		Revision as of 01:54, 9 October 2014
Line 2:		Line 2:

	== Download and Install VM ==		== Download and Install VM ==
	The ~~Dev~~ VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev vm and has many enhancements over the original version. It is a vm that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.		The Slashdev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev VM and has many enhancements over the original version. It is a VM that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

	Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.		Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.
Line 9:		Line 9:

	<pre>ssh: 8022		<pre>ssh: 8022
	http; 1337</pre>		http: 1337</pre>

	For ssh your connection string should be:		For ssh your connection string should be:
Line 15:		Line 15:
	<pre>ssh slash@127.0.0.1 -p 8022</pre>		<pre>ssh slash@127.0.0.1 -p 8022</pre>

	For websites, ~~apache~~ will use the name localhost instead of 127.0.0.1 so you will need to use:		For websites, Apache will use the name localhost instead of 127.0.0.1 so you will need to use:

	<pre>http://localhost:1337</pre>		<pre>http://localhost:1337</pre>

Paulej72: /* Setup the Environment */

2014-10-09T01:46:44Z

Setup the Environment

← Older revision		Revision as of 01:46, 9 October 2014
Line 28:		Line 28:
	git pull		git pull
	</pre>		</pre>

	~~Now we need to install the new code to slash. Here is a script that will help with that. Create a new file called deployslash.sh in the slash home directory and chmod it to 755.~~

	There are a couple of scripts set up in the vm that make deploying and reloading slashcode easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.		There are a couple of scripts set up in the vm that make deploying and reloading slashcode easy. The first script is deployslash.sh and the second is reloadslash.sh. These scripts are in the shash user's home directory. The deployslash.sh script will cd into the slashcode directory and install the slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site. Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.

Paulej72: /* MySQL Updates */

2014-10-09T01:45:59Z

MySQL Updates

@@ Line 34: / Line 34: @@
 == MySQL Updates ==
-We need to update the dev environment to work with the new slashcode.  The update files are normally in /srv/slashdev/slashcode/sql/mysql/.  The upgrades file has the latest updates since that last major version of slashcode.  But here is a listing of the command that need to be run.  Save the code below to a file named upgrades.sql in your vm.
+We need to update the dev environment to work with the new slashcode.  The update files are normally in /srv/slashdev/slashcode/sql/mysql/.  The upgrades file has the latest updates since that last major version of slashcode.  The 14.10 version of the vm is fully up-to-date with with the 14.10 release of the slashcode, so no updates to MySQL are needed.  You will need to add any future DB updates that are listed in the upgrades file to keep the new code working properly.
-<pre>
+MySQL is accessed with root as the user and the database slashdev. To access the DB use the command:
-USE slashdev;
+<pre>mysql -u root slashdev</pre>
 == Update Slash ==

Paulej72: /* Setup the Environment */

2014-10-09T01:40:41Z

Setup the Environment

@@ Line 28: / Line 28: @@
 git pull
 </pre>
 Now we need to install the new code to slash.  Here is a script that will help with that.  Create a new file called deployslash.sh in the slash home directory and chmod it to 755.
-<pre>#! /bin/sh
+There are a couple of scripts set up in the vm that make deploying and reloading slashcode easy.  The first script is deployslash.sh and the second is reloadslash.sh.  These scripts are in the shash user's home directory.  The deployslash.sh script will cd into the slashcode directory and install the slashcode to the appropriate locations and then stop the slash daemon, stop and start Apache, clear the memcache, and finally restart the slash daemon. The reloadslash.sh script does the last steps only and is generally needed when updating templates, vars, and other items within the admin interface of the slash site.  Most changes will not take effect right away due to caching. The reload will empty the caches and unload any running Perl scripts from memory.
 == MySQL Updates ==

Paulej72: /* Download and Install VM */

2014-10-09T01:25:01Z

Download and Install VM

← Older revision		Revision as of 01:25, 9 October 2014
Line 2:		Line 2:

	== Download and Install VM ==		== Download and Install VM ==
	The Dev VM can be downloaded from ~~https~~://~~github~~.~~com/SoylentNews/slashcode_vm/releases/download~~/~~RELEASE_14~~.~~02/slashdev~~.ova. This is a ~~vim~~ that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.		The Dev VM can be downloaded from http://vm.soylentnews.org/Slashdev_14.10.ova. This is the latest Slashdev vm and has many enhancements over the original version. It is a vm that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

	Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.		Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.
Line 18:		Line 18:

	<pre>http://localhost:1337</pre>		<pre>http://localhost:1337</pre>

	~~Apache is turned off in the VM. You will need to turn it on using the command:~~

	~~<pre>apacheclt start</pre>~~

	==Setup the Environment ==		==Setup the Environment ==

Paulej72: /* Download and Install VM */

2014-07-17T22:30:01Z

Download and Install VM

← Older revision		Revision as of 22:30, 17 July 2014
Line 2:		Line 2:

	== Download and Install VM ==		== Download and Install VM ==
	The Dev VM can be downloaded from ~~http~~://~~torrents~~.~~soylentnews~~.~~org~~/. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: ~~http~~://~~torrents~~.~~soylentnews~~.org/.		The Dev VM can be downloaded from https://github.com/SoylentNews/slashcode_vm/releases/download/RELEASE_14.02/slashdev.ova. This is a vim that is designed to run on VirtualBox. Information and downloads of VirtualBox are available here: https://www.virtualbox.org.

	Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.		Once you get the VM downloaded and the VirtualBox up and ruining, you will want to do a '''File:Import Appliance''' in VirtualBox. This will unpack the VM into you environment. Start up the VM and log in with the username and password of slash.

Paulej72: /* MySQL Updates */

2014-06-12T19:44:05Z

MySQL Updates

← Older revision		Revision as of 19:44, 12 June 2014
Line 94:		Line 94:
	ALTER TABLE submissions MODIFY subj VARCHAR(100);		ALTER TABLE submissions MODIFY subj VARCHAR(100);

	# Add new voting ~~feel~~
			# Add new voting field
	# NOTE: this shouldn't be in users, but it makes audioguys job easy, and the schema		# NOTE: this shouldn't be in users, but it makes audioguys job easy, and the schema
	# is already fucking ugly as sin so ....		# is already fucking ugly as sin so ....
	ALTER TABLE users ADD COLUMN willing_to_vote tinyint UNSIGNED DEFAULT 0 NOT NULL;		ALTER TABLE users ADD COLUMN willing_to_vote tinyint UNSIGNED DEFAULT 0 NOT NULL;


	# Disable portscanning by default		# Disable portscanning by default
	INSERT INTO vars (name, value, description) VALUES ('enable_portscan','0','Enable portscanning of proxys');		INSERT INTO vars (name, value, description) VALUES ('enable_portscan','0','Enable portscanning of proxys');


	# Setup Imporved Threaded comments		# Setup Imporved Threaded comments
	INSERT INTO commentmodes (mode, name, description) VALUES ('improvedthreaded','Impoved Threaded','');		INSERT INTO commentmodes (mode, name, description) VALUES ('improvedthreaded','Impoved Threaded','');
	ALTER TABLE users_comments CHANGE mode mode ENUM('flat','nested','nocomment','thread','improvedthreaded') DEFAULT 'improvedthreaded' NOT NULL;		ALTER TABLE users_comments CHANGE mode mode ENUM('flat','nested','nocomment','thread','improvedthreaded') DEFAULT 'improvedthreaded' NOT NULL;

			# Set all users on theraded or nested to improved threaded
	UPDATE users_comments SET mode = 'improvedthreaded' WHERE mode = 'nested' OR mode = 'thread';		UPDATE users_comments SET mode = 'improvedthreaded' WHERE mode = 'nested' OR mode = 'thread';

	# ~~Remove Slashcode Theme and~~ set to default
	~~UPDATE site_info SET~~ value='default~~' WHERE name~~='~~theme'~~;		# Add in var to set if Newsletters are sent to new users by default
			INSERT INTO vars (name, value, description) VALUES ('newsletter_by_default','0','Turn on newsletter sending by default for new users. 0 = off \| 1 = on');


	# Update for longer nicknames		# Update for longer nicknames
Line 115:		Line 122:
	ALTER TABLE users CHANGE nickname nickname varchar(35) DEFAULT '' NOT NULL;		ALTER TABLE users CHANGE nickname nickname varchar(35) DEFAULT '' NOT NULL;
	ALTER TABLE users CHANGE matchname matchname varchar(35);		ALTER TABLE users CHANGE matchname matchname varchar(35);


	# Add admin only for subscription prefs		# Add admin only for subscription prefs
	INSERT INTO vars (name, value, description) VALUES ('subscribe_admin_only', 1, 'Subscription prefs only enabled for admins?');		INSERT INTO vars (name, value, description) VALUES ('subscribe_admin_only', 1, 'Subscription prefs only enabled for admins?');


	# Remove deleted plugins		# Remove deleted plugins
Line 126:		Line 135:
	DELETE FROM site_info WHERE description LIKE '%FireHose%';		DELETE FROM site_info WHERE description LIKE '%FireHose%';
	DELETE FROM site_info WHERE description LIKE '%Tag%';		DELETE FROM site_info WHERE description LIKE '%Tag%';


			# Blocks update
			ALTER TABLE blocks ADD COLUMN default_block tinyint UNSIGNED DEFAULT 0 NOT NULL;
			ALTER TABLE blocks ADD COLUMN hidden tinyint UNSIGNED DEFAULT 0 NOT NULL;
			ALTER TABLE blocks ADD COLUMN always_on tinyint UNSIGNED DEFAULT 0 NOT NULL;
			UPDATE blocks SET default_block = 1 WHERE bid = 'poll' OR bid = 'index_more' OR bid = 'index_qlinks' OR bid = 'top10journals';
			UPDATE blocks SET hidden = 1 WHERE bid = 'features_qlinks' OR bid ='recenttopics' OR bid ='spamurlregexes' OR bid ='subscriber_plug' OR bid ='articles_more' OR bid = 'features_more';
			UPDATE blocks SET ordernum = 100 WHERE bid = 'mysite';
			UPDATE blocks SET ordernum = 3 WHERE bid = 'topcomments';
			UPDATE blocks SET seclev = 500 where bid = 'index_qlinks';
			DELETE FROM blocks WHERE bid = 'newestthree';

			# Remove all dynmaic user blocks or new blocks will not show up
			TRUNCATE TABLE dynamic_users_blocks;

			# Insert site news from old site_news template (Pull from your current site news rather than using this default if you already have it.)
			INSERT INTO blocks (bid, block, seclev, type, description, skin, ordernum, title, portal, url, rdf, retrieve, default_block, always_on) VALUES ('site_news','<!-- begin site_news block -->\r\n\r\nYou should put some site news here that your users might enjoy.\r\n\r\n<!-- end site_news block -->\r\n\r\n',500,'static',NULL,'mainpage',1,'Site News',1,NULL,NULL,0,1,1);

			# Delete slashboxes from all users
			UPDATE users_index SET slashboxes = '';


			# Delet story_never_author for all users to fix author bug (do this each time until bug fixed)
			UPDATE users_index SET story_never_author = '';


			# Allow Reltionship Change Messages to get sent for non subscribers
			UPDATE message_codes SET subscribe=0 WHERE code=12;

	</pre>		</pre>

Crutchy: /* MySQL Updtes */

2014-05-19T08:05:37Z

MySQL Updtes

← Older revision		Revision as of 08:05, 19 May 2014
Line 59:		Line 59:
	This script will be part of the next version of the Dev VM.		This script will be part of the next version of the Dev VM.

	== MySQL ~~Updtes~~ ==		== MySQL Updates ==
	We need to update the dev environment to work with the new slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/. The upgrades file has the latest updates since that last major version of slashcode. But here is a listing of the command that need to be run. Save the code below to a file named upgrades.sql in your vm.		We need to update the dev environment to work with the new slashcode. The update files are normally in /srv/slashdev/slashcode/sql/mysql/. The upgrades file has the latest updates since that last major version of slashcode. But here is a listing of the command that need to be run. Save the code below to a file named upgrades.sql in your vm.