The last Mac I owned had 512kB of memory and no hard drive, but it did have
that newfangled 3.5" floppy drive.

The wider internet probably knows. You might try
https://accc.uic.edu/answer/how-do-i-use-ssh-and-sftp-mac-os-x

On Wed, Jan 16, 2019 at 9:41 AM TheShoff <[email protected]> wrote:

> Also, how would I access the server with SSH (I have a MAC and can use
> Terminal)? I have already set up private and public keys and provided the
> public key to the hosting provider, however I used FTP to login into the
> server. Do you know how I would go about logging in with Terminal?
>
> On Tuesday, January 15, 2019 at 7:59:24 PM UTC-7, Alex Heyden wrote:
>>
>> The server that is hosting the site. The one you're trying to FTP onto.
>> Your quality of life will be greatly improved if you can SSH onto the
>> machine rather than using FTP, because the actual server software that
>> hosts Python processes usually needs to be restarted. It's unlikely (but
>> not unheard of) that you have anything like CPanel controlling a Django
>> instance. It's *probably* going to be GUnicorn or uWSGI, but there's a
>> half dozen options on that front too.
>>
>> I know that all sounds really wishy-washy, but I don't want to mislead
>> you accidentally. The overall architecture isn't that different from a PHP
>> app, but you might not recognize the configuration and file server
>> technologies being used. The further along you get, the easier it'll be for
>> people to figure out what's going on and help you at least figure out what
>> files need to be changed.
>>
>> On Tue, Jan 15, 2019 at 6:39 PM TheShoff <[email protected]> wrote:
>>
>>> Thank you for your response! By host machine, do you mean the machine
>>> (computer) the site was created on or the server that is hosting the site?
>>> I have always worked in PHP and HTML and am used to downloading/uploading
>>> files to the server to make changes.
>>>
>>> On Tuesday, January 15, 2019 at 2:30:44 PM UTC-7, Alex Heyden wrote:
>>>>
>>>> Assuming you're familiar with web technologies in general, you'd make
>>>> these changes on the host machine itself, ideally through the same
>>>> mechanism that handles deployments of source code. Code for application
>>>> logic is often in files called "views.py" or similar, and the HTML will be
>>>> in a folder called "templates" by convention, either near the top of the
>>>> code or contained within the directories (called "applications" in Django)
>>>> that hold server code.
>>>>
>>>> The FTP client is probably the closest you've gotten so far, but
>>>> "denied access" can mean anything from permissions to authentication
>>>> issues. You might want to start there.
>>>>
>>>> On Tue, Jan 15, 2019 at 3:04 PM TheShoff <[email protected]> wrote:
>>>>
>>>>> I am trying to add reCaptcha to an existing Django website that was
>>>>> created by a company we no longer work with. I have server access to the
>>>>> website, but cannot figure out how to edit the files or add the reCaptcha
>>>>> form (I tried to manually add the code into the HTML and .py files and
>>>>> uploading it on my FTP client and was denied access). Do I need to login 
>>>>> to
>>>>> the website using Python to add the reCaptcha form? If so, can someone 
>>>>> tell
>>>>> me how? I am not looking to make any other changes at this time.
>>>>>
>>>>> ***Please note I am new to Django and trying to figure out how it
>>>>> works.***
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Django users" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> Visit this group at https://groups.google.com/group/django-users.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/django-users/da98679f-180b-4433-9c94-faa13e27ec3d%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/django-users/da98679f-180b-4433-9c94-faa13e27ec3d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at https://groups.google.com/group/django-users.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-users/ce4b4cc7-0082-4474-a6c3-d393665f6e32%40googlegroups.com
>>> <https://groups.google.com/d/msgid/django-users/ce4b4cc7-0082-4474-a6c3-d393665f6e32%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/f932eddc-cd5a-4846-8af7-1fa34b6de736%40googlegroups.com
> <https://groups.google.com/d/msgid/django-users/f932eddc-cd5a-4846-8af7-1fa34b6de736%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2Bv0ZYVs0yBJYNFUzfU3o5wsuJun6fB1dguToLDz2Lh4t89dcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to