Update documentation to reflect changes to mediagoblin.ini

[ayleph]

The ​latest documentation still recommends copying mediagoblin.ini to mediagoblin_local.ini. This is now deprecated as we no longer ship mediagoblin.ini, and we instead recommend copying mediagoblin.example.ini to mediagoblin.ini. The documentation should be updated to reflect this.

[Saksham Agrawal]

Hello

I would like to work on this ticket. It will be my first one, so can you please help me out how to submit a patch

[ayleph]

I forgot that make will automatically copy mediagoblin.example.ini to mediagoblin.ini if the file doesn't already exist. So we don't require that the user perform this step themselves, but we do allow it. The part about mediagoblin_local.ini still needs to be removed though.

[ayleph]

Replying to saksham1115:

Hello

I would like to work on this ticket. It will be my first one, so can you please help me out how to submit a patch

Sure! We usually do development on the master branch and submit patches in git-format-patch format. If you want to submit a patch, you should make sure you're up to date with master.

$ cd /path/to/mediagoblin
$ git checkout master
$ git pull

Personally, I like to then create a working branch based off of master for each issue. I do that like this.

$ git checkout -b issue5429

Then apply your changes. When you're finished, you need to export your changes in git-format-patch format. If you're working on a separate branch, you can export your changes from master like this. If you made multiple commits, you might want to squash them into a single commit below running the command below.

$ git format-patch master

Check the patch file(s) and make sure they look good. Also make sure they contain the correct attribution information for you (your preferred name/nickname and email address).

Once you have a patch ready, upload it to here using the Attachments button on this issue. Then change the ticket status to "review." It also helps if you contact someone on IRC to let them know you have a patch ready for review. If there are issues with the patch or if someone needs more information, they'll respond to the ticket.

Edit: Also, if you're working on a ticket, you can claim the ticket to mark it as in-progress.

[ayleph]

Thanks for the patch. There are a few more files that reference mediagoblin_local.ini and it would be good to fix them all at once. I see the following files still refer to mediagoblin_local.ini. The one exception below is relnotes.rst, as that file is simply a collection of historical release notes.

docs/source/siteadmin/configuration.rst
docs/source/siteadmin/deploying.rst
docs/source/siteadmin/media-types.rst
docs/source/siteadmin/production-deployments.rst
docs/source/siteadmin/relnotes.rst
docs/source/siteadmin/theming.rst

Also, there are some old typos in the file you changed that would be good to fix.

- To enable a media type, add the the media type under the ``[plugins]`` section 
- in you ``mediagoblin.ini``. For example, if your system supported image
+ To enable a media type, add the media type under the ``[plugins]`` section in
+ your ``mediagoblin.ini``. For example, if your system supports image

[Saksham Agrawal]

I am extremely sorry for the typos. I didn't see the exception for the relnotes. Patch file 0003 has the fix for the typos. Please don't use the 0002 patch file as i have by mistake changed the relnotes. Will fix it ASAP and upload the new patch file.

[Saksham Agrawal]

0003 and 0004 are the final patch files.

I have changed all the .rst and readme files where I could find the occurrences of "mediagoblin_local.ini".

I am extremely sorry for so many errors.

[Boris Bobrov]

0004 suggest to use mediagoblin_local.ini. Why?

Also, there are too many whitespace changes. For example, in many files you add whitespace after dots. Please remove these whitespace changes.

[ayleph]

Looking at this again, it appears that patches 2 and 3 had some good changes, but then patch 4 pretty much undid everything. Patches 2 and 3 don't apply now, but they give me a place to look for changes that need to be made.

[dpg]

This bit me previously. Updating the documentation now.

[dpg]

Little confused. It seems the online documentation just needs synced with the master branch?

[Ben Sturmfels]

Confirming that these documentation changes are now live. Thanks dpg, Andrew and Boris and Saksham for working on this.