We have website/portal currently successfully running live. There was a module called Lets say "A". Which is already developed.
Client asked to add some more tremendous amount of features and updates to that module.
Now we need to give beta release of this new development to specific group of users and rest of the users will have same old application.
Can anyone suggest a better and a kind of good standard approach to give beta releases on Live Site.
Thanks
Related
I am working with a team to develop a Google Action for an Organisation called 'Rocket Chat'. Now what we want to do is that, to create one main account under that organisation, where frontend and backend will be hosted and also give access of this account to a few Developers. What will be the most efficient way of doing this?. Any ideas or suggestions on how to do that are appreciated. Thanks.
Frontend is hosted on Dialogflow and for backed we are hosting our fulfilment on Firebase. If you want more details on our setup, please visit here => https://github.com/RocketChat/google-action-rocketchat
The "correct" way to do it would be for every developer to use their own account, and share a project with all of them. This also will allow you to have more granular permissions for each developer.
In addition to having ownership of the project, you may also want to have some processes in place to mitigate potential issues. If everyone uses one project, it's possible to run into race conditions if multiple developers upload the same cloud function. The Dialogflow console also may have issues with multiple editors at one time.
For easier development, each developer may want their own separate prototyping project which gives them full control over the environment, and then have some way to integrate their changes into one master project.
i have a project with a friend and its about developing a website which will provide the users with some courses on certain topics.
And we were wondering on how we are going to be updating the lessons notes and posting new ones without any problem. And he said the cpanel provided by the host company will provided a means to post just like on blogs. So i doubted and i'll like to ask if it true or i'll have to code a new page for every topic on the site.
Please i'll appreciate if any one helps me with the truth or a guide on how to do it.
thanks...
A good starting point for you is to use github to host a code repository you start with git. If you use github, you can utilize github pages to host your content for free.
If you already have a hosting framework in mind like WAMP or heroku, let us know and we can provide more specific information on how to push your code up to your application depending on how you're hosting it. But the best starting point for you is to use some sort of version control and the leading version control option is git. You definitely never need to rewrite the same code all over again and version control is essential for managing updates to your code and collaborating with other developers.
This comment mentions a partial roll out in Chrome Web Store. Where can I find that feature? My extension has more than 8,000 users but I don't see any partial roll out feature and I'm afraid to send the next version to all users at the same time.
I don't think it's documented anywhere. And I was wrong!
Documentation link: Control how fast your app reaches users.
In CWS lingo this is called "Controlled Rollout".
If you don’t see the max deploy percentage control, it may be because of the following:
You have less than 10,000 users. Currently the “controlled rollout” feature is only available for items with at least 10,000 users.
You need to upload a newer (higher) version of a package to use the “controlled rollout” feature. We can’t apply a controlled rollout to an already published package, because it may have already reached 100% of users.
It should show on the Edit page after you upload a new version that's not published yet. Here's a mention of it and how it should look:
Also, I've never actually tried using it.
Update: In the new Webstore Dashboard it's called "Partial Rollout" and has the same 10k users requirement.
I am about to start development on an UWP Application. One of the last minute requirements was to be able to support white-labeling the application for our partners. Does anyone have any experience doing this using the Universal Windows Platform that would be willing to give me some insight on resources I should be looking at?
Some basic questions I have is:
Is it possible? I read about it being done with iOS and Android.
How do you create the AppPackage for each partner?
Localization differences? Where one localization may refer to it as one product, but another refers to it as the other product.
Or is this something where I would bundle everything up and send it to the partner to create their own upload? If this is the case, is there a how-to on that?
Some of these might be basic questions, but this is the first time I have created a white-label application, so it is all new to me.
Have just replied to another one topic and looks that screenshot is still needed)
When you submit App to store you can find option:
This way you can make your app visible only to your partners. And you can also register as many apps as you like (each one for separate partner)
Or you can distribute your app thrue Windows Store for Business.
Take a look also at this link, it might be helpful for you
Distribute LOB apps to enterprises
We have a Gmail Contextual Gadget, it is published in Google Apps Marketplace.
For OAuth1.0 to 2.0 migration, as recommended in https://developers.google.com/apps-marketplace/v1migratev2 we created a new version of our Gmail Contextual Gadget, published it in Google Apps Marketplace, and associated it with the old version.
Now, to the question: the old version of the gadget was installed in about 50 domains. What happens to them after September, 30? Do they migrate automatically? Or what do we need to do so that our users could continue using our gadget?
UPD:
As soitof pointed out, Step 4 of the migration guide suggests that we call 'PUT https://www.googleapis.com/appsmarket/v2/upgradableApp/listingID/cwsID/domain'
Yet, I am unsure about how to proceed from here. Namely, what the migration strategy should be.
The first thing is that we don't keep the list of domains where our gadget is installed,
we only have the number of domains. I suppose we could track the requests and build that list.
Here comes the second point: do we fire that PUT requests manually? It is not difficult for our 50 domains, but what if there were, say, 10000? My wild guess would be that we make the old version of our app fire that PUT request automatically, but I am not sure if that's a good idea.
I would welcome some advice, 'best practices', 'guidelines' etc. on how it is usually done.
No they will not migrate automatically, you have to migrate them. Its a simple task you just need a bit of info about your old and new app.
All the info is found here:
https://developers.google.com/apps-marketplace/v1migratev2
UPDATE:
So to migrate you will need two versions of your gadget published, one in the old market place and one in the new one.
So right now you have your old GamV1 gadget listed, you'll need to submit your new one for publishing. Once it is approved, and listed, you can begin the migration. You have to wait till it's published since you need information from its public listing.
You'll need to build a list of domains and perform the PUT on each one manually. I made a script that performed the PUT on a domain name, then made a wrapper script that fed it domains one by one.