¶ Checklist for Creating a Brand New Conference
- DNS
- Add necessary DNS entries for SendGrid. SendGrid can generate a list of required entries.
- A or CNAME pointing to weber
- FontAwesome - Add new conference domain to the domain list of our Fontawesome.com Pro account. Login information is in 1Password shared vault under Fontawesome
- .env file
- Create a local .{DATABASE}.env file for dev servers by copying a similar file from another conference.
- Create the production .env file on our production web server. For NeurIPS, this is /www/neurips.cc/.env
- Modify the secret values that need to be different between conferences leaving the shared ones alone:
- These need to be updated
- DJANGO_SECRET_KEY
- productionhost
- BRAINTREE keys
- CONFERENCE_CURRENT_CONFERENCE
- CONFERENCE_HOMEPAGE_CONFERENCE
- CONFERENCE_BADGE_CRYPTO_KEY
- CONFERENCE_DATABASE
- DJANGO_EMAIL_DEFAULT_FROM
- If IEEE conference, AVENTRI_API_KEY
- Make a new git branch matching the database name
- Create the first conference in manage.py shell
- con = Conferences()
- con.name = “ECCV 2024”
- con.id = 2024
- con.timezone = “Pacific/Honolulu”
- con.startdate = datetime.date(2024, 6, 5)
- con.enddate = datetime.date(2024, 6, 11)
- con.visible = True
- con.save()
- from core.models import Organizations
- org = Organizations()
- org.year_founded = 1990
- org.name = “ECCV”
- org.long_name = “European Conference on Computer Vision”
- org.save()
With the org and conference objects created, you should be able to ./manage.py runserver
- Update the set_conf.sh file to have a function matching the database name
- Apache2
- Set up the /etc/apache2/sites-available/{DATABASE}.conf file based off an existing one.
- Adjust the number of processes and threads to suit the size of the conference.
- run ./fixPermissions
- Database
- Copy the database from a smaller meeting
- Remove unneeded users (a script that does this is in progress)
- Remove unneeded documents.
- Delete registrations, invoices, ccinvoices, page_views,
- Systems Administration
- Create a cron job in the support2 account to run hourly jobs following the pattern of the other conference.