![[Siege, do not ship] SoM devlog CLI](/rails/active_storage/blobs/redirect/eyJfcmFpbHMiOnsiZGF0YSI6NjUyNDcsImV4cCI6IjIwMjYtMDUtMzFUMDM6MzU6MjYuMDcwWiIsInB1ciI6ImJsb2JfaWQifX0=--f8d19fd09ea68ec20341f736ab81bf164996fa63/multipart_constructed.png)
[Siege, do not ship] SoM devlog CLI
CLI that lets you post a SoM devlog for your projects
Followers
No followers yet
Ship Your Project
Get ready!
Once you ship this you can't edit the description of the project, but you'll be able to add more devlogs and re-ship it as you add new features!
Timeline
(test devlog for SoM ship showcase) I considered the potential of users and reviewers alike not reading the conveniently named README,
so I added some checks that tell the user to fix their session.json if it is missing or broken
I added argparse support, the tool now takes project ID+devlog image+devlog text (or a readable file). well, let's test it :P
(this is a test devlog) if you're seeing this, i fiddled around with multipart forms enough to get this devlog submitted
(this is a test devlog) if you're seeing this, i fiddled around with multipart forms enough to get this devlog submitted
Made the functions that write my own multipart form data (apparently, requests can do that itself? woah,,,), but the server was always returning 400 (Bad Request). I found a way to probably fix this. posting this devlog so that the next one can be testing
All this beautifulsoup work just to get the csrf token pf
I also got cookies kind of set up with a separate session.json file so that i don't leak my session cookies :p
wuh, forgot to actually write my text for this… apologies. the image here would have been a screenshot of the last post, since that’s a pretty clear demonstration. for this update, I made added the filename to the request (the last devlog has a “devlog[file]“ filename inherited from the request field :P ), and found a way to get the server response (redirect) back