TabbycatDebate/tabbycat

View on GitHub
docs/locale/es/LC_MESSAGES/install/heroku.po

Summary

Maintainability
Test Coverage
msgid ""
msgstr ""
"Project-Id-Version: tabbycat\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-12-31 10:38-0400\n"
"PO-Revision-Date: 2020-07-05 17:17\n"
"Last-Translator: \n"
"Language-Team: Spanish\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.7.0\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Crowdin-Project: tabbycat\n"
"X-Crowdin-Project-ID: 364715\n"
"X-Crowdin-Language: es-ES\n"
"X-Crowdin-File: /develop/docs/locale/en/LC_MESSAGES/install/heroku.po\n"
"X-Crowdin-File-ID: 1315\n"
"Language: es_ES\n"

#: ../../install/heroku.rst:5
msgid "Installing on Heroku"
msgstr ""

#: ../../install/heroku.rst:7
msgid "When running Tabbycat on the internet, we set it up on `Heroku <http://www.heroku.com/>`_. The project is set up to be good to go on Heroku, and it works well for us, so if you'd like to run it online, we recommend that you do the same. Naturally, this requires you to have a Heroku account."
msgstr ""

#: ../../install/heroku.rst:9
msgid "There are two ways to do this: a **short way** and a **long way**. Most people should use the short way. The long way requires some familiarity with command-line interfaces and Git, and requires a :ref:`local installation <install-local>` as a prerequisite, but makes it easier to :ref:`upgrade versions <upgrade-heroku>` later on and (unlike the short way) allows you to import data from CSV files."
msgstr ""

#: ../../install/heroku.rst:12
msgid "The short way"
msgstr ""

#: ../../install/heroku.rst:13
msgid "Click this button:"
msgstr ""

#: ../../install/heroku.rst:18
msgid "This is the easiest way to deploy an instance of Tabbycat online. It requires no technical background."
msgstr ""

#: ../../install/heroku.rst:20
msgid "If you don't already have a Heroku account, it'll prompt you to create one. Once you're logged in to Heroku, choose a name for your installation, then scroll down and click **Deploy**. Once it's finished, click **View** and follow the prompts. Once finished, open the site and from there you can easily set up a demo data set (if you just want to learn Tabbycat) or use the data importer to set up a real tournament."
msgstr ""

#: ../../install/heroku.rst:22
msgid "During the setup process, Heroku will ask you to verify your account by adding a credit card. A standard Tabbycat site *will not charge* your card — charges only accrue if you deliberately add a paid service in the Heroku dashboard."
msgstr ""

#: ../../install/heroku.rst:24
msgid "If you can't access a credit card, you can instead install a limited version, which we call \"Tabbykitten\". However, Tabbykitten cannot send any e-mails or handle as much public traffic. We therefore strongly recommend it only as a last resort, and even then only for small tournaments.  `Use this link to set up a Tabbykitten site <https://heroku.com/deploy?template=https://github.com/TabbycatDebate/tabbycat/tree/kitten>`_."
msgstr ""

#: ../../install/heroku.rst:27
msgid "The long way"
msgstr ""

#: ../../install/heroku.rst:28
msgid "The long way sets you up with more control over your environment.  Because you'll clone `our GitHub repository`_, it'll be easier for you to :ref:`upgrade your app <upgrade-heroku>` when a new version is released.  You'll also have the flexibility to make and contribute updates to the source code.  We recommend it if you have experience with Git.  It's also easier with this method to import CSV files using the command-line importer, so if you have a very large tournament, this might make importing initial data easier."
msgstr ""

#: ../../install/heroku.rst:30
msgid "We've tested these instructions successfully on Windows, Linux and macOS."
msgstr ""

#: ../../install/heroku.rst:33
msgid "Requisite technical background"
msgstr ""

#: ../../install/heroku.rst:35
msgid "You need to have at least a passing familiarity with command-line interfaces to get through the longer traditional method. We'll talk you through the rest."
msgstr ""

#: ../../install/heroku.rst:37
msgid "When we say \"command shell\", on Windows we mean **Command Prompt**, and on Linux and macOS we mean **Terminal** (or your favourite command shell)."
msgstr ""

#: ../../install/heroku.rst:39 ../../install/heroku.rst:100
msgid "Advanced users"
msgstr ""

#: ../../install/heroku.rst:42
msgid "Tabbycat is a `Django <https://www.djangoproject.com/>`_ project. As such, it can be installed on any web platform that supports Django, using any SQL system that Django supports. Just be aware that we haven't tried any other platform."
msgstr ""

#: ../../install/heroku.rst:45
msgid "Short version of the long way"
msgstr ""

#: ../../install/heroku.rst:47
msgid "We provide a \"short version\" for experienced users. Don't just copy and paste these commands before you understand what they do! If things aren't set up perfectly they can fail, so it's important to supervise them the first time you do them. If this is all new to you, read the long version of the instructions below."
msgstr ""

#: ../../install/heroku.rst:56
msgid "If you want to :ref:`import tournament data <importing-initial-data>` from CSV files, :ref:`install Tabbycat locally <install-local>`, put your CSV files in ``data/yourtournamentname``, then::"
msgstr ""

#: ../../install/heroku.rst:68
msgid "1. Install dependencies"
msgstr ""

#: ../../install/heroku.rst:70
msgid "Install the `Heroku Command Line Interface (CLI) <https://devcenter.heroku.com/articles/heroku-cli>`_, then log in with the command ``heroku login``."
msgstr ""

#: ../../install/heroku.rst:72
msgid "If you don't already have **Git**, follow the `instructions on the GitHub website <https://help.github.com/articles/set-up-git>`_ to set up Git."
msgstr ""

#: ../../install/heroku.rst:75
msgid "2. Set up a local installation"
msgstr ""

#: ../../install/heroku.rst:77
msgid "If you don't already have a local installation, follow the instructions on the page for your operating system, listed below, to set up a local installation."
msgstr ""

#: ../../install/heroku.rst:79
msgid "When downloading the source code, you **must** take the option involving cloning the GitHub repository using Git. In the macOS and Windows instructions, this means the option described in the \"Advanced users\" box. To do so, use these commands:"
msgstr ""

#: ../../install/heroku.rst:86
msgid "Do not download the .tar.gz or .zip file and extract it."
msgstr ""

#: ../../install/heroku.rst:88
msgid ":ref:`install-linux`"
msgstr ""

#: ../../install/heroku.rst:89
msgid ":ref:`install-osx`"
msgstr ""

#: ../../install/heroku.rst:90
msgid ":ref:`install-wsl`"
msgstr ""

#: ../../install/heroku.rst:91
msgid ":ref:`install-windows`"
msgstr ""

#: ../../install/heroku.rst:93
msgid "If you do already have a local installation, update to the latest version using:"
msgstr ""

#: ../../install/heroku.rst:103
msgid "It's not *strictly* necessary to have a fully functional local installation if you don't want to import data from CSV files. But it certainly helps."
msgstr ""

#: ../../install/heroku.rst:106
msgid "3. Deploy to Heroku"
msgstr ""

#: ../../install/heroku.rst:110
msgid "Navigate to your Tabbycat directory::"
msgstr ""

#: ../../install/heroku.rst:114
msgid "Run the script to deploy the app to Heroku. Replace ``yourappname`` with your preferred URL. Your website will be at ``yourappname.herokuapp.com``."
msgstr ""

#: ../../install/heroku.rst:120
msgid "This script has other options that you might find useful. Run ``python deploy_heroku.py --help`` for details."
msgstr ""

#: ../../install/heroku.rst:122
msgid "When this script finishes, it will open the app in your browser. It should look something like this:"
msgstr ""

#: ../../install/heroku.rst:127
msgid "4. Import tournament data locally"
msgstr ""

#: ../../install/heroku.rst:129
msgid "Steps 4 and 5 are optional; there are other methods of :ref:`importing data <importing-initial-data>`. However the following method is most useful for large tournaments where manual entry would be tedious."
msgstr ""

#: ../../install/heroku.rst:131
msgid "Step 4 is the same as the process described in :ref:`importtournament-command`."
msgstr ""

#: ../../install/heroku.rst:135
msgid "Place your CSV files in ``data/yourtournamentname``, as described in :ref:`importing-initial-data`."
msgstr ""

#: ../../install/heroku.rst:137
msgid "Create a new, blank local database::"
msgstr ""

#: ../../install/heroku.rst:141
msgid "It's normally easiest to name your local database after your app name, so that if you have multiple sites, you know which one relates to which."
msgstr ""

#: ../../install/heroku.rst:143
msgid "Reconfigure ``DATABASES`` in your settings_local.py file to point to this new database."
msgstr ""

#: ../../install/heroku.rst:145
msgid "Activate your virtual environment::"
msgstr ""

#: ../../install/heroku.rst:149
msgid "Run initial migrations on your blank local database::"
msgstr ""

#: ../../install/heroku.rst:154
msgid "Import your tournament data into your blank local database::"
msgstr ""

#: ../../install/heroku.rst:158
msgid "If your data's not clean, it might take a few attempts to get this right. We recommend either destroying and recreating the database (``dropdb``, ``createdb``), or wiping it using ``dj flush``, before retrying."
msgstr ""

#: ../../install/heroku.rst:160
msgid "Check it looks like how you expect it to look, by starting your local installation::"
msgstr ""

#: ../../install/heroku.rst:165
msgid "5. Push the local database to Heroku"
msgstr ""

#: ../../install/heroku.rst:167
msgid "Once you're happy with how your local import went, you can push the local database to Heroku."
msgstr ""

#: ../../install/heroku.rst:169
msgid "This step wipes the Heroku database clean, and replaces it with the contents of your local database. If you have any data on the Heroku site that isn't also in your local database, **that data will be lost** and will not be recoverable."
msgstr ""

#: ../../install/heroku.rst:171
msgid "If you have multiple Heroku sites, you may find that the ``heroku`` commands refuse to run, prompting you to specify an app. If so, add ``--app yourappname`` to each ``heroku`` command."
msgstr ""

#: ../../install/heroku.rst:173
msgid "Enable maintenance mode. This takes the site offline, to ensure that no-one can possibly create or change any data on the site while you're pushing a new database up::"
msgstr ""

#: ../../install/heroku.rst:177
msgid "Reset the database. (Caution: This permanently deletes all information on your Heroku database!)"
msgstr ""

#: ../../install/heroku.rst:183
msgid "Push your local database to Heroku::"
msgstr ""

#: ../../install/heroku.rst:187
msgid "You might need to specify your local PostgreSQL credentials by adding ``PGUSER=yourusername PGPASSWORD=******** PGHOST=localhost`` to the *beginning* of that command. (This sets environment variables to those values for the duration of that one command.)"
msgstr ""

#: ../../install/heroku.rst:189
msgid "Disable maintenance mode::"
msgstr ""

#: ../../install/heroku.rst:195
msgid "Heroku options you may want to change"
msgstr ""

#: ../../install/heroku.rst:197
msgid "If you have a large tournament, you may want to customize your Heroku app. This section provides some guidance on upgrades and settings you may wish to consider. Some of these configurations require you to have the `Heroku Command Line Interface (CLI) <https://devcenter.heroku.com/articles/heroku-cli>`_ installed."
msgstr ""

#: ../../install/heroku.rst:202
msgid "Upgrading your database size"
msgstr ""

#: ../../install/heroku.rst:204
msgid "The free plan of `Heroku Postgres <https://elements.heroku.com/addons/heroku-postgresql>`_, \"Hobby Dev\", should work for most small tournaments. For large tournaments, however, you may find that you exceed the 10,000-row limit of this plan. It's difficult to give general guidance on how many rows you're likely to use, because it depends on which features of Tabbycat you use (*e.g.*, if you use adjudicator feedback). But to give some idea:"
msgstr ""

#: ../../install/heroku.rst:206
msgid "Australs 2016, which had 74 teams, 8 preliminary rounds and heavily used adjudicator feedback, ended up at around 30,000 rows."
msgstr ""

#: ../../install/heroku.rst:207
#, python-format
msgid "The Asia BP championships 2017 had 100 teams, 6 preliminary rounds, and mandatory feedback (i.e. 100% return rates) used 15,000 rows."
msgstr ""

#: ../../install/heroku.rst:208
msgid "A 3 vs 3 tournament with 54 teams, 5 preliminary rounds, and which only lightly used adjudicator feedback ended up using around 4,500 rows"
msgstr ""

#: ../../install/heroku.rst:210
msgid "If you need more than 10,000 rows, you'll need to upgrade to a paid Heroku Postgres Plan. The 10,000,000 rows allowed in the lowest paid plan, \"Hobby Basic\", should certainly be more than sufficient."
msgstr ""

#: ../../install/heroku.rst:212
msgid "If you're not sure, you can always start at Hobby Dev—just be prepared to `upgrade <https://devcenter.heroku.com/articles/upgrade-heroku-postgres-with-pgbackups>`_ during the tournament if you run close to capacity."
msgstr ""

#: ../../install/heroku.rst:215
msgid "Custom domain names"
msgstr ""

#: ../../install/heroku.rst:217
msgid "Your Heroku app will be available at ``yourappname.herokuapp.com``. You may want it to be a subdomain of your tournament's website, like ``tab.australasians2015.org``. If so, you'll need to configure your custom domain and SSL. Instructions for both are in the Heroku Dev Center:"
msgstr ""

#: ../../install/heroku.rst:219
msgid "`Custom Domain Names for Apps <https://devcenter.heroku.com/articles/custom-domains>`_"
msgstr ""

#: ../../install/heroku.rst:220
msgid "`Heroku SSL <https://devcenter.heroku.com/articles/ssl>`_"
msgstr ""

#: ../../install/heroku.rst:222
msgid "The custom domain name basically requires two things: a DNS ``CNAME`` entry on your website targeting ``yourappname.herokuapp.com``, and the custom domain configured on Heroku using ``heroku domains:add tab.yourwebsite.com``.  You'll also need to provide an SSL certificate for your custom domain and add it using the ``heroku certs:add`` command."
msgstr ""

#: ../../install/heroku.rst:225
msgid "HTTPS"
msgstr ""

#: ../../install/heroku.rst:227
msgid "All Tabbycat sites deployed to Heroku redirect all traffic to HTTPS by default."
msgstr ""

#: ../../install/heroku.rst:229
msgid "For a myriad of reasons, we strongly advise against disabling this. But if for some reason you need to run on plain HTTP, you can do this by setting the ``DISABLE_HTTPS_REDIRECTS`` config variable in Heroku to ``disable`` (see `Heroku documentation on config vars <https://devcenter.heroku.com/articles/config-vars>`_). The value of the config var must be ``disable``; if it's anything else, HTTPS redirects will remain in place."
msgstr ""

#: ../../install/heroku.rst:231
msgid "Most modern browsers, after having been redirected by a site to HTTPS once, remember that that site requires HTTPS and go there for all subsequent visits even if the user typed in a plain http\\:// address. It may do this because it cached the HTTP 301 permanent redirect, stored an HSTS entry and/or tagged its session cookie to require HTTPS. If, after disabling HTTPS on your Tabbycat site, you find that you're still being redirected to HTTPS, first try a browser or computer that *hasn't* visited the site before. If that works, then remove the relevant entry from your (original) browser's cache, HSTS set and cookies, and try again."
msgstr ""

#: ../../install/heroku.rst:234
msgid "Time zone"
msgstr ""

#: ../../install/heroku.rst:236
msgid "If you want to change the time zone you nominated during deployment, you can do so by going to the `Heroku Dashboard <https://dashboard.heroku.com/>`_, clicking on your app, going to the **Settings** tab, clicking **Reveal Config Vars** and changing the value of the ``TIME_ZONE`` variable. This value must be one of the names in the IANA tz database, *e.g.* ``Pacific/Auckland``, ``America/Mexico_City``, ``Asia/Kuala_Lumpur``.  You can find a `list of these on Wikipedia <https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List>`_ in the 'TZ\\*' column."
msgstr ""

#: ../../install/heroku.rst:239
msgid "SendGrid account details"
msgstr ""

#: ../../install/heroku.rst:241
msgid "By default, Heroku will automatically create a SendGrid account for you. For small tournaments, this should work fine. For larger ones, though, SendGrid typically doesn't allow new accounts to send so many emails without additional vetting. This vetting is separate to the verification you did for your Heroku account, and as far as we're aware, it can't be done until you send your first email, by which time it's probably too late."
msgstr ""

#: ../../install/heroku.rst:243
msgid "If you're running a large tournament, you may wish to use your own SendGrid account instead. The free tier probably won't suffice after the trial period, but the Essentials tier should be more than adequate. If you're a student and have the `GitHub Education Pack <https://education.github.com/pack>`_, you might find the SendGrid plan here useful."
msgstr ""

#: ../../install/heroku.rst:245
msgid "If you set up and use your own SendGrid account, you can remove the SendGrid add-on from your Heroku app. The SendGrid add-on is only necessary if you wish to use Heroku's auto-created SendGrid account."
msgstr ""

#: ../../install/heroku.rst:247
msgid "To set up your app to use your own SendGrid account:"
msgstr ""

#: ../../install/heroku.rst:251
msgid "`Sign up for a SendGrid account <https://sendgrid.com/pricing/>`_, if you don't already have one."
msgstr ""

#: ../../install/heroku.rst:253
msgid "`Create an API key <https://app.sendgrid.com/settings/api_keys>`_ in your SendGrid account."
msgstr ""

#: ../../install/heroku.rst:255
msgid "There are `instructions for how to do this in the SendGrid documentation <https://sendgrid.com/docs/User_Guide/Settings/api_keys.html>`_. The only permission that is needed is the \"Mail Send\" permission, so you can turn off all others if you want to be safe."
msgstr ""

#: ../../install/heroku.rst:257
msgid "Set the following config vars in Heroku Dashboard (or using the Heroku CLI, if you have it):"
msgstr ""

#: ../../install/heroku.rst:259
msgid "``SENDGRID_USERNAME`` should be set to ``apikey`` (not your username)."
msgstr ""

#: ../../install/heroku.rst:260
msgid "``SENDGRID_PASSWORD`` should be set to your API key, which will start with ``SG*******``."
msgstr ""

#: ../../install/heroku.rst:262
msgid "The `Heroku SendGrid instructions <https://devcenter.heroku.com/articles/sendgrid#setup-api-key-environment-variable>`_ to do something with ``SENDGRID_API_KEY`` are **incorrect**. We figured this out by contacting SendGrid support staff. Use the above config vars instead."
msgstr ""

#: ../../install/heroku.rst:268
msgid "Upgrading an existing Heroku app"
msgstr ""

#: ../../install/heroku.rst:270
msgid "For most users, we recommend starting a new site for every tournament, when you set up the tab for that tournament. There's generally not a pressing need to upgrade Tabbycat after a tournament is concluded, and every time you deploy a new site, you'll be using the latest version at the time of deployment."
msgstr ""

#: ../../install/heroku.rst:272
msgid "To upgrade an existing Heroku-based Tabbycat app to the latest version, you need to *deploy* the current version of Tabbycat to your Heroku app. There are several ways to do this. We list one below, primarily targeted at users with some background in Git."
msgstr ""

#: ../../install/heroku.rst:274
msgid "The essence of it is that you need to `create a Git remote <https://devcenter.heroku.com/articles/git#creating-a-heroku-remote>`_ for your Heroku app (if you don't already have one), then `push to it <https://devcenter.heroku.com/articles/git#deploying-code>`_."
msgstr ""

#: ../../install/heroku.rst:276
msgid "You should **always** :ref:`back up your database <backups>` before upgrading Tabbycat."
msgstr ""

#: ../../install/heroku.rst:278
msgid "You'll need both Git and the Heroku CLI, and you'll need to be logged in to the Heroku CLI already."
msgstr ""

#: ../../install/heroku.rst:280
msgid "Take a backup of your database::"
msgstr ""

#: ../../install/heroku.rst:284
msgid "If you haven't already, clone our Git repository and check out the master branch::"
msgstr ""

#: ../../install/heroku.rst:289
msgid "If you've already cloned our Git repository, don't forget to pull so you're up to date::"
msgstr ""

#: ../../install/heroku.rst:294
msgid "Check to see if you have a Git remote already in place::"
msgstr ""

#: ../../install/heroku.rst:300
msgid "If you do, the name of the remote will be on the left (``heroku`` in the above example), and the URL of your Git repository will be on the right. In the example above, our Tabbycat site URL would be ``mytournament2018.herokuapp.com``; the Git remote URL is then ``https://git.heroku.com/mytournament2018.git``."
msgstr ""

#: ../../install/heroku.rst:302
msgid "If a Git remote URL for your Tabbycat site *doesn't* appear, then create one::"
msgstr ""

#: ../../install/heroku.rst:307
msgid "If you tab many tournaments, it'll probably be helpful to use a name other than ``heroku`` (say, ``mytournament2018``), so that you can manage multiple tournaments."
msgstr ""

#: ../../install/heroku.rst:309
msgid "Push to Heroku::"
msgstr ""

#: ../../install/heroku.rst:313
msgid "This will take a while to complete."
msgstr ""