tag:support.appharbor.com,2010-11-23:/discussions/problems/104071-video-not-foundAppHarbor: Discussion 2019-10-24T06:46:42Ztag:support.appharbor.com,2010-11-23:Comment/475762582019-09-02T03:58:22Z2019-09-02T03:58:22ZVideo not found<div><p>Hi Jan,</p>
<p>I can see that the file is indeed being copied to the output directory correctly, so you probably just need to configure the <code>mp4</code> mime type. Take a <a href="https://appharbor.tenderapp.com/discussions/problems/54577-mimemap-and-iis-version-on-appharbor#comment_32402030">look at my answer in this discussion</a> for information on how to configure that.</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/475762582019-09-03T05:40:21Z2019-09-03T05:40:21ZVideo not found<div><p>Rune,<br>
that has fixed the problem, thank you!<br>
Jan</p></div>ToniTurektag:support.appharbor.com,2010-11-23:Comment/475762582019-09-04T02:40:14Z2019-09-04T02:40:14ZVideo not found<div><p>Hi Jan,</p>
<p>Good to hear that fixed it, let me know if there's anything else I can help with!</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/475762582019-09-04T10:13:16Z2019-09-04T10:13:16ZVideo not found<div><p>Rune,<br>
Furthermore, I'm only wondering if I can read the output of the "git describe" command similar to the commit id which I'm reading with: System.Web.Configuration.WebConfigurationManager.AppSettings["appharbor.commit_id"]</p>
<p>Cheers,<br>
Jan</p></div>ToniTurektag:support.appharbor.com,2010-11-23:Comment/475762582019-09-07T17:55:30Z2019-09-07T17:55:30ZVideo not found<div><p>Hi Jan,</p>
<p>We only write the commit ID stored as part of the <a href="https://support.appharbor.com/kb/api/builds-api-2#detail">branch and commit information on the build entry available</a>, and that's independent of the version control system used -- we could potentially expand the API to allow for more descriptive commit information (which could then in turn be integrated with AppHarbor's git repository hosting/deployments). Would be curious to hear you use case for including this information so we can take that into consideration?</p>
<p>Best,<br>
Rune</p></div>runetag:support.appharbor.com,2010-11-23:Comment/475762582019-09-23T13:57:39Z2019-09-23T13:59:13ZVideo not found<div><p>Hi Rune,</p>
<p>sorry for the late reply, I was on holiday for a few weeks...</p>
<p>I use to use at least two branches in my git repository. The master and the develop branch. When I merge the develop branch into the master, I tag the new commit on the master branch with a new incremented version number. Afterwards, I merge back the master into the develop branch. When I then use the command "git describe" on the master branch, I get the current version number. When I use it on the develop branch, I get the version number plus the number of added commits on the develop branch as an appendix to the version number. This behaviour makes it possible to directly indicate two things when using the "git describe" command:<br>
1.: If I only see a version number, I know I'm on the master branch and this is a stable version<br>
2.: If I see an appendix to the version number, I know I'm on the develop branch and also how many steps in front of the stable version (which works like an additional version number level)</p>
<p>So e.g. if I have the last commit on the master branch tagged "v1.0.0" and I have two more commits on the develop branch I (for example) get "v1.0.0-2-gabc123".</p>
<p>Hope my explanation was clear!</p>
<p>Regards,<br>
Jan</p></div>ToniTurektag:support.appharbor.com,2010-11-23:Comment/475762582019-09-24T08:55:53Z2019-09-24T08:55:53ZVideo not found<div><p>I forgot to say: Of corse I want to show the current version number in my app.</p>
<p>Regards,<br>
Jan</p></div>ToniTurek