gmemstr/pogo

Audio feed generator and CMS

kubernetes and infrastructure nerd. probably working on private repositories, mostly doing new projects on my private git forge.

mastodon

pogo's Issues

Nicer frontend

The current frontend is a bit hacked together, I want to avoid JS frameworks but if it's small enough I might consider it.

Add proper encryption to users.json

Would like to add some sort of encryption to user login, I also plan to move this to a more modern cookie & POST login system soon but basic HTTP login works fine for the early stages. Would like to focus on getting encryption working because that's the more difficult part.

Fully test Docker image

I currently natively develop in Windows 10 and don't want to go through the hassle of managing and testing Docker with each new build, I will be working on a script for TravisCI if possible but I want some help putting together some docs and fully testing the Dockerfile. Basically

• Test to ensure the Dockerfile builds and properly runs Pogo
• Write up steps to fetch Docker image and running it

I'm fairly new to Docker so this will be a learning experience for me as well 😋

Not include the dependencies in the repo

You are saving all the dependencies in the "vendor" folder, right?

This is not a good practice because it increases the size of the repository and makes more difficult to upgrade the dependencies to newer versions.

You have a Godeps file in your repository. You should use this instead host the dependencies at the repository.

Move main frontend to Vue.js + enhancements

I'll be taking a couple days off actual development and focusing on things like promotion and documentation, so I'll leave a couple issues open if anyone would like to tackle less mission-critical objectives. I will still be active in this repository (I have a couple more things to do before working exclusively on documentation for a bit), so feel free to open any other issues or create pull requests.

Regardless, the primary frontend could probably be moved over to Vue.js, using vue-router for individual episode selection and such. This could also help reduce initial page load if we hide the actual <audio> tag behind something. We would need to preserve admin CSS editing in some fashion as well, so keeping the classes as-is is important.

• Move frontend to single-page app using Vue.js & vue-router
• Make <audio> tags render dynamically to reduce initial load time
• Implement either the same or better theming functionality
• Look into creating code injection or custom templates editable by admins

Obviously not one pull request needs to cover all these goals but it would make a huge improvement to the frontend design and functionality wise.

Please see project 2.0.0.