On 05/15/2017 01:14 PM, Ralph Bean wrote: > Cheers on os.stg.fedoraproject.org! > > I'd love to have waiverdb[1] be the first app on os.fedoraproject.org > once it is ready. Do you guys have any estimates of when we could > start messing with that in both stg and prod? (Maybe we could help > you work out kinks if we can try deploying to os.stg.fp.o even before > os.fp.o is ready?) Well, it's pretty hard to estimate as we have so much going on and this is not the super top priority. That said, I think its not going to be too long. We have our staging instance up. We have successfully deployed an app from git and rebuilt it on changes. Next step we really need is to get a wildcard ssl cert so we can point people to the apps without going though a bunch of hoops (firefox won't show them to you because of HSTS, chrome/chromium you have to start with a insecure option). Hopefully that cert will happen soon and then the main thing left in my mind is to get apps setup in ansible. ie, ansible creates the project and such so we don't need to do any clicking around or cli stuff. We could probibly use help with that if anyone has used the openshift ansible modules. After that I could see trying to setup waverdb in stg. > > I put a due date in my project planning of "June 30th" for when > waiverdb would be available in a production env. It's not "make or > break" if we don't hit that date, but if os.fp.o won't be available for > many months, maybe we should go ahead with VM-based ansible deployment > in the meantime. I think that is doable. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
