Fixing local SSL setup for testing
Got rid of some complicated setup and switched to dnsmasq to handle subdomains locally.
Marketing discussions
Might get featured in marketing content from cloudflare.
Because of how much I use their products and also me talking about it so many times in my tweets.
Because of how much I use their products and also me talking about it so many times in my tweets.
Solution Found: Wildcard SSL + CDN for
Test.install.so now delivered via CloudFlare.
Any new accounts that get created would also have SSL+CDN, with no worries of certificate renewal for me.
Super happy today!
Any new accounts that get created would also have SSL+CDN, with no worries of certificate renewal for me.
Super happy today!
Back at appbasics
Reviewing what's left to be done.
Dreading the task of SSL
- renew certs with certbot
- apply them to my nginx
- make api call to bunnycdn and update it there.
- restart my app containers
I am currently on step 1, lol
Dreading the task of SSL
- renew certs with certbot
- apply them to my nginx
- make api call to bunnycdn and update it there.
- restart my app containers
I am currently on step 1, lol
Have you tried Caddy? It has built in lets encrypt support and you don't need to do any setup
Researching simpler solution for wildcard SSL
Basically I have to renew SSL and then submit it to bunnycdn, update nginx and restart all containers.
Need to figure out simpler way
Need to figure out simpler way
Created column_styles
I thought it would be easier to deal with styles later on and instead of working on a general purpose solution I should just save the updated column ratios and call it a day
Worked on roadmap
My friends asked me why I haven't launched yet. So I felt I need to answer that to myself first. I think it all comes down to if the product works, it used to work fine until I added more features which I felt were necessary for launch. Adding these features without tests was a mistake which lead to delays in getting this off the ground.
Today I made a short list of pending things which I want to tackle this weekend
- check why installing app on iOS doesn't provide an icon on home screen.
- rewrite styles with mobile screens in mind, previous implementation only thought about large display.
- store column and image resize info once after dragging ends instead of current multiple requests while dragging.
- add a landing page
- enable sending invites for admin
- setup some basic log monitoring
- test SSL expiration which will happen on 7th May.
- send invites
Today I made a short list of pending things which I want to tackle this weekend
- check why installing app on iOS doesn't provide an icon on home screen.
- rewrite styles with mobile screens in mind, previous implementation only thought about large display.
- store column and image resize info once after dragging ends instead of current multiple requests while dragging.
- add a landing page
- enable sending invites for admin
- setup some basic log monitoring
- test SSL expiration which will happen on 7th May.
- send invites
fixing sidebar to show correct navigation links on page change
look at whats left to do on
still fixing column resizer
I need to remove the handlebars around both sides of a column and only put separators between columns to adjust ratio of width between them.
OR I need t let this column resizer go away and just release what I have.
OR I need t let this column resizer go away and just release what I have.
Deployed all pending commits
more work on editor
- add editor support for missing data from Notion API for pages such as full width or not.
continue testing onboarding flow and fix issues
update create new app form to also include root page selector
Fix issues with subdomain handling
Resume work on
Looking at where I left off and trying to finish enough things to get the app ready for users.
fix crash when newly created app doesn't have navbar yet
more work on onboarding steps
Rework how I store styles
Previous approach didn't use selectors. Instead depended on internal data model to decide where to apply a particular set of properties.
New approach uses CSS selectors and join table with page id so I can do the following
- add style for a particular element on a page
- add style for a particular element on multiple pages
- add style for a particular element type on a page or multiple pages
New approach uses CSS selectors and join table with page id so I can do the following
- add style for a particular element on a page
- add style for a particular element on multiple pages
- add style for a particular element type on a page or multiple pages