Fix bugs in my Django project
Budget: $30 – $250 USD
https://calenvy.com/dash/gmail_PSEXRW/?asdf logging in on this page is missing the CSRF token
The search feature after logging in at the top left of the page needs to activate the search feature from the People widget at the right side of the dash :) and there should be a button to clear the search and start over :)
[] and then run crontab -e
[] the crontab command needs to run at reboot starting the server via runserver.sh in the web folder 36369 is the port
also, the usernames for User objects should probably be email addresses for now or the @username that people select when the modal opens up asking for a password and that particular username
The /dash/alias should probably be aliased at /alias (or /username) so when you login, if your username selected is “blah” (the username selector is at the modal that appears when a new account is registered and when someone is logged in) then simply have the url https://calenvy.com/blah load up like all modern websites where it shows you your profile.
What would be really cool based on the previous item (/alias aka /username) is if you simply allow people to make stuff public so that users that are not logged in to the website can visit your calenvy.com/username and simply see whatever from your dashboard is made public [huge win]
Also, if you don’t mind adding the crawling mechanism back to the codebase where when you login, it can crawl your imap :) i think celery_worker is kind of too much of a pain so it probably is easier to simply have a parallel process opened up whenever there is a crawl happening and just have the code from celery_worker simply added to the bitbucker.org/calenvy/web repo :)
Logging to live.log in the /home/calenvy/logs folder is having issues, it would be nice if it worked.
The search feature after logging in at the top left of the page needs to activate the search feature from the People widget at the right side of the dash :) and there should be a button to clear the search and start over :)
[] and then run crontab -e
[] the crontab command needs to run at reboot starting the server via runserver.sh in the web folder 36369 is the port
also, the usernames for User objects should probably be email addresses for now or the @username that people select when the modal opens up asking for a password and that particular username
The /dash/alias should probably be aliased at /alias (or /username) so when you login, if your username selected is “blah” (the username selector is at the modal that appears when a new account is registered and when someone is logged in) then simply have the url https://calenvy.com/blah load up like all modern websites where it shows you your profile.
What would be really cool based on the previous item (/alias aka /username) is if you simply allow people to make stuff public so that users that are not logged in to the website can visit your calenvy.com/username and simply see whatever from your dashboard is made public [huge win]
Also, if you don’t mind adding the crawling mechanism back to the codebase where when you login, it can crawl your imap :) i think celery_worker is kind of too much of a pain so it probably is easier to simply have a parallel process opened up whenever there is a crawl happening and just have the code from celery_worker simply added to the bitbucker.org/calenvy/web repo :)
Logging to live.log in the /home/calenvy/logs folder is having issues, it would be nice if it worked.