I started a new project with Core Data and Cloud kit enabled (from Apple 2022 WWDC tutorial and Xcode 14.2) . I added a container. I synced a few data, sync is obviously working because I can delete the app and retrieve automatically all the data from the cloud.
My problem is that I can't see any data on the cloud kit portail. My requests don't return any object with public or private database, but I can confirm my entity is synced with its attributes. My guess is I'm seeing the wrong zone.
I read that the zone com.apple.coredata.cloudkit.zone should be selected in the Zone droplist but I never had this choice. In the Xcode console it confirms that the sync is done with this zone. Any clue how to get this option?
Found out : I used two different iCloud Apple ID (one with my dev account and App Store, one for Apple services and docs). You must use the same Apple ID on the device than the one with dev account. Apple should allow to merge accounts.
Related
I've installed Oracle Cloud app with hope that I can manage my instances(turn them off, on or restart) but I can't see such option. Is there a way to do that within app or It's just a health status?
At present you can not turn things off and on again via the app. Currently (30 Nov 2020), you can view details about the following types of resources in the mobile app.
Compute instances
Block volumes
Object Storage
Load balancers
Autonomous Transaction Processing
Autonomous Data Warehouse
You can find its current documentation via here - https://docs.cloud.oracle.com/en-us/iaas/Content/GSG/Concepts/mobile.htm
I'm trying to setup continuous deployment via the Aure Portal.
When doing this via the VSTS account (let's call it "VSTS Account A") which is owned by the same account owner as Azure, everything works fine.
In this case I'm trying to configure continuous deploymenet from source code held in another VSTS account (let's go with Account B).
The Azure account owner is not the Account B owner but is an admin (member of Organization Administrators) for Account B. The owner is also listed explicitly as a member of at least one project within Account B.
The problem is that when it commes to configuring "Deployment source" within the app service section, Account B is not listed as an option to choose from.
I've followed various links (e.g. part 4 of this page) about linking the VSTS account with an Azure account but still no joy. There are a couple of problems here:
The Azure classic portal has a New button within the Visual Studio Team Services section but when I choose Link To Existing, I get the following message:
Make sure you’re the account owner. If you are, maybe your account is
linked to another Azure subscription or connected to another Azure
Active Directory
Account B is not linked to another Azure Subscription or Azure AD.
The new portal doesn't even have an option to attempt to link a different account, plus the menu link says "Team Services Account Preview" so whether the Preview status has something to do with it, I don't know.
I'd have thought this would be a relatively common use case, has anyone had any joy setting up something similar?
I was finally able to choose the relevant account by making the VSTS principal a co-admin in the Azure account which contains the web app, signing in as that user and changing the directory to use from the the user dropdown menu (top-right). Note, the user account in question is already an administrator for a different Azure account, just to complicate matters further. I only had the option to change the directory once the user was a member of multiple directories.
So I finally got it configured and committing code to the specified branch was triggering a deploy. However, it transpires that setting up continuous deployment from within Azure gives you limited scope and I got constant errors which were not straightforward to fix.
I ended up getting it working properly by following these instructions:
Build: https://www.visualstudio.com/en-us/docs/build/apps/aspnet/ci/build-aspnet-4
Deploy: https://www.visualstudio.com/en-us/docs/build/apps/cd/deploy-webdeploy-webapps
Configuring it all from within VSO gives you a lot more clarity about what's actually happening.
When doing the initial setup, I had to go through an authentication step with the Azure account I was trying to deploy to and that process launches a pop-up window which was getting blocked so I missed it at first.
The initial build and deploy were fine but I was getting a build error when being triggered from a code commmit. This is because the Build Definition --> Variables --> BuildConfiguration value was set back to Release even though I set it to the correct value for my project when doing the initial configuration. Once I updated that, the next commit triggered the build which in turn created the artifact which in turn triggered the deploy which went through fine.
Googler from the future here, I had the same problem and came across a really good article called "DevOps: Connecting VSTS to Azure by Ken Muse" enter link description here
This worked like a charm for me from the first try!
Parse is shutting down soon and having a deadline for Database Migration 28th April 2016.
Currently I still have 2 production apps that is live on parse.com, but due to some tight schedule, I am afraid that I won't able to complete my parse database migration on time. Is there any way that can keep my app traffic prioritize even after the due date 28th April 2016?
I can't find any contact to Parse Support Team, that's why I'm asking the question here.
Thank you.
https://github.com/ParsePlatform/parse-server/wiki/Migrating-an-Existing-Parse-App
28th April 2016 is the RECOMMENDED date for migrating to self hosted MongoDB.
Just migrate the database. You don't need to migrate everything now. You have more time to do it. I will explain you supposing you will migrate to https://www.back4app.com
After the migration, both parse.com dashboard, back4app.com dashboard, https://api.parse.com and https://parseapi.back4app.com will be connecting to the same recent migrated database in back4app servers. It means that parse.com api and dashboard will keep working and the same data will also be available both in parse.com and back4app.com.
Therefore until the date you publish the new app connecting to parseapi.back4app.com, all your current customers will keep connecting to api.parse.com that will connect to the migrated database in the back4app servers. Everything will be working fine.
Then you have to test and prepare all your app and once you are comfortable you publish the new version of your app. When published, your clients will start updating their apps. The updated ones will be connecting to back4app.com and others to parse.com. But everything will be working fine because it is the same database.
The scenario described above will work until Feb 2017 and that's why it is important to start the migration process and then the publishing of the new app as soon as possible. So your clients will have more time to update their apps.
I want to understand how people are handing an update to a production app on the Parse.com platform. Here is the scenario that I am not sure about.
Create an called myApp_DEV. The app contains a database as well as associated cloud code.
Once testing is complete and ready for go-live I will clone this app into myApp_PRD (Production version). Cloning it will copy all the database as well as the cloud code.
So far so good.
Now 3 months down the line I want have added some functionality which includes adding some cloud code functions as well as adding some new columns to the tables in the db.
How do I update myApp_PRD with these new database structure. If i try to clone it from my DEV app it tells me the app all ready exists.
If I clone a new app (say myApp_PRD2) from DEV then all the data will be lost since the customer is all ready live.
Any ideas on how to handle this scenario?
Cloud code supports deploying to production and development environments.
You'll first need to link your production app to your existing cloud code. this can be done in the command line:
parse add production
When you're ready to release, it's a simple matter of:
parse deploy production
See the Parse Documentation for all the details.
As for the schema changes, I guess we just have to manually add all the new columns.
I am new windows azure user. I have gotten selected for 90 days trial account and I am able to upload my ASP.NET MVC3 application to my account. My site is also running now. After I did publish my site, I added more model, views and controller to my proramme. Now I can not find a way to update my application. I can again publish my application but update option is not there. I want to update my new code only but the package option is creating full application. How I can update the new code to my site in windows azure cloud?
[Changed spelling]
With Windows Azure you can publish/update an application following ways:
Log into you Windows Azure account. Select you hosted server name and at the top panel you will see "Upgrade" option, when you will use this option you will be given a chance to select your CSPKG and CSCFG file from local file system or from Windows Azure storage. Once you selected new or updated CSPKG, your current running service will bee upgraded.
You can also use Windows Azure PowerShell Cmdlets to upgrade your current running hosted service using "Update-Deployment" command:
2.1 http://wappowershell.codeplex.com/
You can other 3rd party applications created using Windows Azure Service Management API to upgrade/manage your current running hosted service.
3.1 http://wapmmc.codeplex.com/
3.2 http://www.cerebrata.com/Products/CloudStorageStudio/Default.aspx
Note: With Visual Studio if you again publish your application, it will delete the current running hosted service and then create the new on so for update it is not the good one.
Finally based on your question about partial update, that is not supported. Even when you make a single line change in your code the deployment will be considered a full deployment even when the action is "update/upgrade". There is no diff package deployment so evertime you update your Windows Azure application, you will use the newly created CSPKG file and upgrade your hosted application.
Regarding partial update: If you have multiple Roles, you may choose to upgrade a single role (so that would be a partial update of the deployment). For a given Role, all code is redeployed. If you're running more than one instance, the update will be rolled out across groups of instances, not all instances at once.
For updates such as static content: if you move these into blob storage (a great place for css, jquery, images, etc.), then you may update this content by simply uploading new items to blob storage individually. These updates don't require any code to be rebuilt or redeployed.
If you're in dev mode (e.g. non-production), you may enable Web Deploy, which then allows very fast updates of your app to the running instance. This only works in single-instance mode, and it's great when doing frequent code+test cycles.