Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ajf]

For some reason, I decided to tell BassMakesPaste the full process I use for adding and updating server-sent plugins. Here it is:

The "process" as such is as follows:

• I create the directory /Users/ajf/Projects/2011/Gang Garrison 2/Plugins/Approvals/YYYY-MM-DD Author - pluginname on my computer (and suffix (update) if it's an update)
• I create the subdirectory v1 (approved) in that directory (if I don't approve it, I'll rename that to just v1 and create a v2 (approved) with the fixed version and so on)
• The plugin zip is downloaded to v1 (approved) and extracted into its own subdirectory (if the zip was plugin.zip, a directory called plugin would be made)
• If it's a new plugin, I'll look at the gml files in my favourite text editor. If it's an existing plugin, I use diff on the command line with the previous version and the new version to see what's changed.
• If I'm happy with it, I copy the zip file to htdocs/pluginname.zip in the copy of the repository on my machine
• I run my script (which is in the repository) like so: php md5.php htdocs/pluginname.zip - It'll rename the zip file so it has the MD5 hash in its name after an @, create a .md5 file, and update data.json. (If it's a new plugin, I need to edit data.json to add the author's name and the forum thread number)
• I quickly check I didn't screw anything up with git status then add the changes to git with git add .
• I commit the changes, usually with this format: git commit -m "Updated Author's 'pluginname'"
• I push the changes to the repository on GitHub: git push
• I ssh into the ganggarrison.com server and update the copy of the repository there (hence updating /plugins/): ssh ganggarrison.com "cd /var/www/plugins && git pull"

And that's it. I'm not sure why I bothered going into such detail, but that's the actual process.

[Lorgan]

For some reason, I decided to tell BassMakesPaste the full process I use for adding and updating server-sent plugins. Here it is:

• If it's a new plugin, I'll look at the gml files in my favourite text editor. If it's an existing plugin, I use diff on the command line with the previous version and the new version to see what's changed.

Lies!

[ajf]

Are you accusing me of not actually checking your plugins' updates?

Because I would never, ever do that, would I?

[Phantom Brave]

Simplified version:

* Verify plugin is not malicious
* Upload to /var/www/plugins
* Run /var/www/plugins> php md5.php htdocs/pluginarchive.zip
* Update data.json if plugin is new
* Do git on the server
** Hope AJF/Medo don't get mad at you for doing things backwards

[ajf]

Simplified version:

* Verify plugin is not malicious
* Upload to /var/www/plugins
* Run /var/www/plugins> php md5.php htdocs/pluginarchive.zip
* Update data.json if plugin is new
* Do git on the server
** Hope AJF/Medo don't get mad at you for doing things backwards

I won't be mad, but make sure you use the correct author on your commits

[Phantom Brave]

git amend