Activity
It's really, really well done. Props to the authors!
I'm definitely migrating over some older apps too! :)
Posted in Page Specific Javascript
This is a really great question Michael. Do you have examples of what kind of Javascript you intend to run on specific pages? I can give you some generic advice, but it's always easier to understand with some examples.
Posted in Multitenancy with Apartment Gem
Are you executing pg_dump
manually from the command line? I've noticed that when it's run without the user option, it defaults to the current operating system username. Wondering if that is what's happening.
I haven't had the time to find any solution to that recently. Hopefully someone can leave a comment if they find a solution!
Posted in Setup MacOS 10.10 Yosemite Discussion
Sounds like your server isn't running. You can run "brew info postgres" to get the instructions for starting the postgres server.
It should be in the top right if you click on "Account" in the navigation too.
Posted in File Uploads with Refile Discussion
Yes you can. This isn't specific to Refile, but just some regular Javascript hitting the browser File api. http://jsfiddle.net/LvsYc/
Posted in Setup MacOS 10.10 Yosemite Discussion
Try restarting your terminal. That usually fixes it.
Posted in Setup MacOS 10.10 Yosemite Discussion
Yep they should! I use ZSH too, but it supports almost the exact same syntax.
Posted in Multitenancy with the Apartment gem
You probably want to create a Rake task to run through your existing users and create their tenants. You could also do this in the Rails console. Just loop through each user and then create the tenant and that should be it.
Another solution is you could catch the error when the tenant doesn't exist and to create it then. This would let you roll it out and they would each be created as they were used.
I'd probably recommend the first option because it means that all your users are running on the same code all the time. It's generally better to have consistent data than not.
The &:symbol
syntax basically just turns a method name into a block to call. What it is doing is sorting the array of events by the simple_calendar_start_time
column. First we select out the ones for the day in the select block and then we sort by the start time so that all the events are filtered and in order.
That make more sense?
What isn't working for you?
Posted in Admin for the specific case
I think Pundit would make a lot of sense for this. With Pundit, you're passing in the user and you can use it to evaluate whether the user has access to the object. Instead of putting the authorization logic int a method on the Work model, you can do it inside the Pundit class instead. That makes things a lot better organized and manageable for you.
Definitely need to get on this one! It's one of the most requested things and I just need to sit down and do it. I'm just using the Stripe JS library coupled with the Rubygem. The JS turns the card into a token, sends it to the server, and the server charges the card and updates the user. That's about it.
I'll make sure to bump this topic up in the queue so I can record it soon.
Just shovel those onto the csv outside of the records loop. Pass in the values you want and they should show up at the bottom.
Posted in Coffeescript Instantiation
Haha! Always the simplest things producing the hardest problems.
I would imagine so, but you'd probably want to ask on their Github issues to be sure. This is probably just more of a database configuration thing than anything with apartment or Rails.
Hey Francisco,
Sounds like you'd be better off making one User model and then adding roles to them instead with Rolify and Pundit. I'd definitely recommend doing this.
If you do want to keep the separate models, you have a couple options.
- You can have separate urls and they choose which type of user they are and get directed to the correct devise login URL.
- You could override the controller to search through each model to find the correct user. This solution gets pretty nasty quickly and isn't flexible for future changes. If you still want to do that, you can attempt something like this: http://blog.frankzhao.com.au/2014/12/single-sign-on-for-two-different-user-models-with-devise/
Yes you can! Just add that attribute to the company and you can use that.