Plutonic Rainbows

I started by removing the .env files from my repository and adding them to my .gitignore so they would not be tracked in the future. After committing and pushing these changes, I still needed to remove the .env files and their contents from every past commit. To do this, I created a fresh bare clone of my repository, used git filter-repo to rewrite the commit history without the .env file, and then force-pushed the updated history back to the remote repository.

By taking these steps, I hopefully eliminated all traces of sensitive data from my repository’s history. Now, with the .env files completely gone, I can safely make my repository public withoutworrying about exposing API credentials.

I'm excited to announce that after seven weeks of development, my application is finally live on AWS! You can check it out here.

I'll be sharing a detailed summary of the project soon, including the challenges I faced and the solutions I came up with to bring it to production.

In no order, I found something of interest in all of these.

• Seefeel - Everything Squared

• Propaganda - Propaganda

• Actress - Statik

• mark s. williamson - folklore, facts & fables 1: seabirds

• Bibio - PHANTOM BRICKWORKS II

• Sarah Davachi and Dicky Bahto - Music For A Bellowing Room

• Wewrkbund - Skalpafloi

• Milan W. - Leave Another Day

• Chris & Cosey - Elemental 7

• Elizabeth Parker - Future Perfect

• Fennesz - Mosaic

I’ve been quite busy over the past few days. I’ve reconfigured the backend to use the National Renewable Energy Project API, marking the third and final API switch. Everything appears to be working smoothly now, but I’ll use this weekend for local testing before deploying it to AWS.