3,860 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Probably having a session id / token on server side for each client session running. An endpoint as well to be called to update session information when the client leaving event is detected.
Looks like you needed a virtual host for your project
You need to add an entry on your hosts file as well so it knows where to find ip address 184.108.40.206.
I think you might need to do deep linking within the android implementation. I know this guys
branch.io have deep linking solutions for this. It might be worth checking out
Replied to AccessTokens For Machine To Machine Clients
Normally you would have sessions on the client application that will store the access token for a given duration. If the session expires after a set time - it means the client application / machine will logout and have to call the login API / request access token API.
Server side implementation should be such that it can issue a token and save it in a db. Sample db could look like this
`id` BIGINT(20) NOT NULL, `access_token` INT(11) DEFAULT NULL, `client_id` INT(11) DEFAULT NULL, `expires_timestamp` INT(11) DEFAULT NULL, `date_created` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP()
So basically it can create unique access_tokens per client machine that expires after a set time. So the auth server should validate that the token is still valid before allowing the request to proceed.