Back
Similar todos
Switched my Song routes to use flask_restx, and I now have all my routes using flask_restx. 
#rhymecraft
Spent some more time switching the API to using flask_restx. #rhymecraft
Moved my API routes into a 'resources' folder to keep things a little more organized and since that's the pattern in the Flask-Vuetify template I like. #rhymecraft
More super-boring chores: Switched the imports so that `flask routes` would work, to help me figure out why a particular route was 404ing (now fixed). #rhymecraft
configure flask-restful to work with app 
#changeloghost
make first rest api with flask
Fixed an annoying db-related error with the #rhymecraft flask code that was causing it to error when I tried to query the API when running it on my laptop.
Got an auth-protected API route working
Switched main API endpoints to api.2markdown.com with backward compatibility for old routes. 
#2markdown
Refactored UI App: Split a context and moved routes so rewriting urls work better. 
#userowl
Move two song-related routes from api/__init__.py to api/songs.py (actually did this yesterday) #rhymecraft
👨💻 continue with flask
create an flask blueprint for api. #changeloghost
Switch my API calls to be in a single backend.js file as I think that'll keep things organized as things get complicated and it's working nicely in the Vuetify app I'm building for an Upwork client of mine. #rhymecraft
refactored a scraper app to use django-q more effectively
👨💻 more flask
tested out flask-admin - works, but decided not to spend any more time configuring auth #changeloghost
Fixed a bug that was preventing auth from working in prod b/c Apache was stripping the auth header before passing it to my Flask app.
refactored new project to use django-q and hooks which made the project start to update itself more than I was updating it.