dolphin-emu/www
1
0
Fork 0
mirror of https://github.com/dolphin-emu/www.git synced 2024-11-23 09:29:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README, TODO, and CONTRIBUTING

Browse Source
This commit is contained in:
Pierre Bourdon 2018-07-21 15:22:19 +02:00
parent 942aa36c7c
commit bdd60862b5
3 changed files with 4 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CONTRIBUTING.md
View File

@ -25,7 +25,7 @@ require more involved staging.
Running a testing instance locally
----------------------------------
First of all, create a Python 2.6 or 2.7 virtual environment and make sure you
First of all, create a Python 3.6+ virtual environment and make sure you
are in it (``echo $VIRTUAL_ENV``). Then install all the required dependencies
with ``pip``:
@ -46,16 +46,7 @@ the ``settings.py`` file (in the ``dolweb/`` directory):
MEDIA_URL = '/m/user/'
STATIC_URL = '/m/static/'
Then run ``syncdb`` to create a default database. Set up a user when it asks you
to - this user is required to access the admin part of the website:
python manage.py syncdb
After you've done this, you need to update the database models:
python manage.py makemigrations
And then apply those updates:
Then run ``migrate`` to create a default database.
python manage.py migrate

3
README.md
View File

@ -3,7 +3,7 @@ Dolphin Emulator Official Website
https://dolphin-emu.org/
Technologies: Django (Python 2.x), HTML and CSS, using Twitter Bootstrap.
Technologies: Django (Python 3), HTML and CSS, using Twitter Bootstrap.
Author: mostly Pierre Bourdon (delroth@dolphin-emu.org).
@ -24,6 +24,7 @@ Quick overview
translation layer) and the guides (stored in the Dolphin Wiki).
* Media: serves the screenshot gallery.
* Homepage: serves the homepage.
* Update: serves update metadata information to users.
Licensing
---------

8
TODO
View File

@ -1,15 +1,7 @@
* Porting to Python 3 and latest Django (currently on old versions).
* Using more of django-annoying where it makes sense, particularly @render_to.
* Provide some fake data sets to use as initial database contents.
* Download system rework: currently the download types are hardcoded, which was
a terrible idea and is now blocking us to add things like Android downloads,
updated Ubuntu builds, etc.
* Should be a DownloadableItem: {version, url, autodetection_thingy} in DB.
* Then need a script to port old data to the new format.
* Download UI: too confusing for users, way too many versions displayed on the
downloads page. Simplify the view with two side by side options: stable or
latest. Explain the benefits. Have links to a more complete downloads page