Does this actually work at all with react-router 4?

[ensemblebd]

Just curious. It took incredible effort to figure out how to properly implement react-router, and more specifically, react-tap-event-plugin. The documentation is trash. Yours is sufficient, but just barely.

Has anyone used this with react-router 4 successfully?

Am almost at the point of scrapping all these user created systems, and just implementing the whole thing myself from ground up. Can't find a single working system that just straight up works.

[jameschetwood]

Subscribing

[ensemblebd]

FYI I was able to get it working. Man the documentation on all of these packages makes this tough.
There were tons of issues I had going on. But I'll see about working up a repo for anyone interested , with a working sample.
It relies upon modified accounts-ui and accounts-material-ui forks (in my profile already), which are comprised of merged resultant from all existing forks from all the people that forked these repos already to fix issues the author won't.
Will reply back once I have that prepped and upped.

[derwaldgeist]

Hey, I would be interested 😊

[ensemblebd]

Guten tag :)
The client we were hired by to develop a project for, ended up scrapping their ambition/funding before we got anywhere significant.
So this boilerplate is about a year old project that we briefly worked on for a couple weeks.
It's not production level quality, definitely dev sandbox only.
Nevertheless, here it is:
https://github.com/ensemblebd/meteor-react-boilerplate-devops

The adjusted repo's for a functional auth system

You'll notice the usage of the local "packages" folder in root, as per meteor's recommendation for overriding packages published to atmosphere.
And so the modified packages are (as per readme usage, and git submodules):
https://github.com/ensemblebd/accounts-ui
https://github.com/ensemblebd/accounts-material-ui

I won't be able to provide any support, but hope it helps.
Just now gave it a good once-over (fresh install from nothing to boot) before pushing up to public repo. And it works still.
Please note:
It uses smtp for email, and can only register on mobile app (per it's original intended app design).
Use Robo3T to modify user role post-registration to become an admin (or register abcdwhatever@mycompany.com) which it checks for, and then you can use the website login (server side admin area). Grep/replace "mycompany.com" to your own intended domain.
Or just edit the settings.json and switch the flag for "forceMobileInDev" to true.. then open up http://localhost:3000 and chrome scale it down to look like a phone.

Side notes

FYI I was using the JetBrains IDE for this (Webstorm). **On Windows. ** If you don't, the npm commands work fine too.. On windows.
Last I touched this, it compiled fine, ran fine, and tested fine on Android and web. And supports building to APK for publishing on app store if you have you ssh keys configured.
Since it's using DDP, you can throw your mongo database anywhere you want. Check the ./buildrun/ folder.
IOS was on the todo list, but I don't see why it wouldn't work for it.
The facebook and google oauth is barely functional, so you might need to tweak the local repo's a bit. But database auth works fine.
Just fork those, and replace the git submodules in your project. Tweak way.

Retrospect

Am honestly pretty underwhelmed by the accounts-ui system. Going forward I'd probably choose to use something else.
Hopefully i nuked/sterilized all the company and client stuff in there. Think i got it all.

[derwaldgeist]

Thanks for sharing!