DIMMiN Notes

My working notes related to the development of dimmin.com.

Clear Filters

2023-06-24

Read more

2023-06-20

  • Updated the Heroku CLI
  • The site is now accessible using the subdomain www.dimmin.com
    • This still re-routes to a version of the app without the SSL certificate, but that will be a change that I need to make in the actual DIMMiN App itself.
    • For whatever reason this is not a problem on chrome browsers, but edge keeps giving me issues. Not sure exactly why but edge was just being a pain in the butt.
    • Occasionally can access the site using dimmin.com, but that might just be an issue with my personal devices
      • Specifically having trouble accessing it on mobile from my own device
  • Began using Anaconda to manage Virtual Environments
  • Transferred credentials for Environment Variables
  • Got a Local Version of the DIMMiN App up and running on my new laptop
  • Updated the Copyright at the bottom of the screen (found in base.html) so that it always displays the current year
  • Added a Staging environment and app (though it's not really used)
  • Updated the DIMMiN App in Production
  • Updated the app so that http requests redirect to https

Read more

2023-06-19

  • Was on tech support with Namecheap for support for about an hour. They recommended I make my Host Name Records:
    • CNAME - @ - dimmin.com.herokudns.com
    • CNAME - www - www.dimmin.com.herokudns.com
  • Recommended I reach out to Heroku's tech support

Read more

2023-06-01

  • Installed a local version of the DIMMiN App
  • Created a Virtual Environment to install app dependencies
  • Downloaded PostgreSQL
  • Fixed the pg_config missing error but ran into another one when trying to install psycopg2.

Read more

2023-05-30

Read more

2023-05-23

Overall, I learned a lot today. I decided to go with ChatGPT's Option 3: Content Embedding method of rendering javascript in posts. This means that I'll host the javascript on AWS, then call it from an S3 bucket in an HTML tag in the text editor. When configuring the CORS Permissions, I was required to specify the domains that can access the S3 bucket and was required to add the header of http:// or https://. I don't want to add my SSL Certificate then have to re-configure this later. I spent most of today trying to configure my SSL certificate (something I've been putting off for a while now). It's not working quite yet but I'll try again Thursday at the latest to see if I can get this up and running.

Read more